Description of problem: module-build-service should not raise a python exception when a build fails. You get bug reports for python exceptions. ;) Version-Release number of selected component: module-build-service-2.20.0-1.fc30 Additional info: reporter: libreport-2.10.1 cmdline: /usr/bin/python3 /usr/bin/mbs-manager build_module_locally --file /home/mcatanzaro/Projects/fedora-flatpaks/epiphany/epiphany.yaml --stream master crash_function: build_module_locally exception_type: RuntimeError executable: /usr/bin/mbs-manager interpreter: python3-3.7.3-3.fc30.x86_64 kernel: 5.1.16-300.fc30.x86_64 runlevel: N 5 type: Python3 uid: 1000 Truncated backtrace: manage.py:195:build_module_locally:RuntimeError: Module build failed Traceback (most recent call last): File "/usr/bin/mbs-manager", line 11, in <module> load_entry_point('module-build-service==2.20.0', 'console_scripts', 'mbs-manager')() File "/usr/lib/python3.7/site-packages/module_build_service/manage.py", line 265, in manager_wrapper manager.run() File "/usr/lib/python3.7/site-packages/flask_script/__init__.py", line 417, in run result = self.handle(argv[0], argv[1:]) File "/usr/lib/python3.7/site-packages/flask_script/__init__.py", line 386, in handle res = handle(*args, **config) File "/usr/lib/python3.7/site-packages/flask_script/commands.py", line 216, in __call__ return self.run(*args, **kwargs) File "/usr/lib/python3.7/site-packages/module_build_service/manage.py", line 195, in build_module_locally raise RuntimeError("Module build failed") RuntimeError: Module build failed Local variables in innermost frame: local_build_nsvs: None yaml_file: '/home/mcatanzaro/Projects/fedora-flatpaks/epiphany/epiphany.yaml' srpms: [] stream: 'master' skiptests: False default_streams: [] offline: False platform_repofiles: [] platform_id: None confdir: '/home/mcatanzaro/Projects/fedora-flatpaks/epiphany' dbdir: '/home/mcatanzaro/Projects/fedora-flatpaks/epiphany' dbpath: '//home/mcatanzaro/Projects/fedora-flatpaks/epiphany/.mbs_local_build.db' dburi: 'sqlite:////home/mcatanzaro/Projects/fedora-flatpaks/epiphany/.mbs_local_build.db' params: {'local_build': True, 'default_streams': {}} username: 'mcatanzaro' yaml_file_path: '/home/mcatanzaro/Projects/fedora-flatpaks/epiphany/epiphany.yaml' fd: <_io.TextIOWrapper name='/home/mcatanzaro/Projects/fedora-flatpaks/epiphany/epiphany.yaml' mode='r' encoding='UTF-8'> filename: 'epiphany.yaml' handle: <FileStorage: 'epiphany.yaml' (None)> modules_list: [<ModuleBuild epiphany, id=2, stream=master, version=3020190714214626, scratch=False, state 'failed', batch 0, state_reason "('Connection aborted.', ConnectionResetError(104, 'Connection reset by peer'))">] stop: <function make_simple_stop_condition.<locals>.stop_condition at 0x7f3ed14f1ea0>
Created attachment 1591034 [details] File: backtrace
Created attachment 1591035 [details] File: cgroup
Created attachment 1591036 [details] File: cpuinfo
Created attachment 1591037 [details] File: environ
Created attachment 1591038 [details] File: mountinfo
Created attachment 1591039 [details] File: namespaces
Created attachment 1591040 [details] File: open_fds
*** Bug 1734596 has been marked as a duplicate of this bug. ***
This message is a reminder that Fedora 30 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora 30 on 2020-05-26. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '30'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 30 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 30 changed to end-of-life (EOL) status on 2020-05-26. Fedora 30 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.