You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The Build started, but failure happened during post build operations should be reported only if the build id is already available. But it seems that this is not always case. See following log:
[2022-05-09 14:00:41,004 hotness.hotness_consumer INFO] Handling anitya msg '963085fd-7a66-47fe-bf24-a1f451c5d65c'
[2022-05-09 14:00:42,846 hotness.validators.mdapi INFO] Comparing upstream 5.0.0 against repo 4.1.2-2.fc30
[2022-05-09 14:00:42,847 hotness.validators.mdapi INFO] 5.0.0 is newer than 4.1.2-2.fc30
[2022-05-09 14:00:44,445 bugzilla.bug INFO] Bug 1996066 missing attribute 'bug_status' - doing implicit refresh(). This will be slow, if you want to avoid this, properly use query/getbug include_fields, and set bugzilla.bug_autorefresh = False to force failure.
[2022-05-09 14:00:44,701 hotness.notifiers.bugzilla INFO] Created bug: #1996066 NEW - m@rtinbriza.cz - mediawriter-5.0.0 is available
[2022-05-09 14:00:44,701 hotness.notifiers.bugzilla INFO] Filled a new bug '[https://bugzilla.stage.redhat.com/show_bug.cgi?id=1996066' ](https://bugzilla.stage.redhat.com/show_bug.cgi?id=1996066%27)
[2022-05-09 14:00:44,702 hotness.notifiers.fedora_messaging INFO] publishing topic 'hotness.update.bug.file'
[2022-05-09 14:00:44,866 hotness.builders.koji INFO] Cloning '[https://src.stg.fedoraproject.org/rpms/mediawriter.git' ](https://src.stg.fedoraproject.org/rpms/mediawriter.git') to '/var/tmp/thn-vojyvz6e'
Using mediawriter.spec
/ 0.0 B Elapsed Time: 0:00:00
- 0.0 B Elapsed Time: 0:00:00
[2022-05-09 14:00:47,532 hotness.use_cases.package_scratch_build_use_case ERROR] Package scratch build use case failure
Traceback (most recent call last):
File "/usr/local/lib/python3.9/site-packages/hotness/builders/koji.py", line 168, in build
cmd_output = sp.check_output(
File "/usr/lib64/python3.9/subprocess.py", line 424, in check_output
return run(*popenargs, stdout=PIPE, timeout=timeout, check=True,
File "/usr/lib64/python3.9/subprocess.py", line 528, in run
raise CalledProcessError(retcode, process.args,
subprocess.CalledProcessError: Command '['rpmbuild', '-D', '_sourcedir .', '-D', '_topdir .', '-bs', '/var/tmp/thn-vojyvz6e/mediawriter.spec']' returned non-zero exit status 1.
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/usr/local/lib/python3.9/site-packages/hotness/use_cases/package_scratch_build_use_case.py", line 56, in build
result = self.builder.build(request.package, request.opts)
File "/usr/local/lib/python3.9/site-packages/hotness/builders/koji.py", line 188, in build
raise BuilderException(
hotness.exceptions.builder_exception.BuilderException: Build started, but failure happened during post build operations:
Command '['rpmbuild', '-D', '_sourcedir .', '-D', '_topdir .', '-bs', '/var/tmp/thn-vojyvz6e/mediawriter.spec']' returned non-zero exit status 1.
StdOut:
error: Bad source: ./MediaWriter-5.0.0.tar.gz: No such file or directory
I should look what is happening there
The text was updated successfully, but these errors were encountered:
Zlopez
changed the title
Build started, but failure happened during post build operations before rpmbuild started
Wrong error message when the build didn't started yet
May 9, 2022
Zlopez
added a commit
to Zlopez/the-new-hotness
that referenced
this issue
May 9, 2022
Hotness didn't checked the build_id variable for value when creating error
message and erroneously reported that the build already started.
This commit is adding the check for zero together with new test.
Fixesfedora-infra#456
Signed-off-by: Michal Konečný <mkonecny@redhat.com>
Hotness didn't checked the build_id variable for value when creating error
message and erroneously reported that the build already started.
This commit is adding the check for zero together with new test.
Fixes#456
Signed-off-by: Michal Konečný <mkonecny@redhat.com>
The
Build started, but failure happened during post build operations
should be reported only if the build id is already available. But it seems that this is not always case. See following log:I should look what is happening there
The text was updated successfully, but these errors were encountered: