Learn more about these different git repos.
Other Git URLs
https://copr-be-dev.cloud.fedoraproject.org/results/praiskup/ping/srpm-builds/00846264/build-00846264.rsync.log
Warning: Permanently added '172.25.154.25' (ECDSA) to the list of known hosts. receiving incremental file list rsync: link_stat "/var/lib/copr-rpmbuild/results/*" failed: No such file or directory (2) sent 8 bytes received 101 bytes 218.00 bytes/sec total size is 0 speedup is 0.00 rsync error: some files/attrs were not transferred (see previous errors) (code 23) at main.c(1659) [Receiver=3.1.3] rsync: [Receiver] write error: Broken pipe (32)
The traceback is:
[2019-09-11 13:34:45,400][ ERROR][backend.worker-3-PC.builder.mr][__init__.py:download_results:315] Traceback (most recent call last): File "/usr/share/copr/backend/daemons/worker.py", line 211, in do_job mr.check_build_success() # raises if build didn't succeed File "/usr/share/copr/backend/mockremote/__init__.py", line 309, in check_build_success raise MockRemoteError("Build {} failed".format(self.job.task_id)) backend.exceptions.MockRemoteError: Build 846264 failed During handling of the above exception, another exception occurred: Traceback (most recent call last): File "/usr/share/copr/backend/mockremote/__init__.py", line 313, in download_results self.builder.download_results(self.job.results_dir) File "/usr/share/copr/backend/mockremote/builder.py", line 163, in download_results self.rsync_call(self.resultdir, target_path) File "/usr/share/copr/backend/mockremote/builder.py", line 160, in rsync_call raise BuilderError(err_msg) backend.exceptions.BuilderError: Failed to download data from builder due to rsync error, see the rsync log file for details.
Production here as well: https://copr.fedorainfracloud.org/coprs/praiskup/ping/build/1031861/
Metadata Update from @praiskup: - Issue tagged with: bug
Metadata Update from @praiskup: - Issue assigned to praiskup
Commit c0dc91f fixes this issue
Metadata Update from @praiskup: - Issue status updated to: Open (was: Closed)
Still there's the traceback, it doesn't keep the build in running state (after #1014), but still it doesn't make sense to print stuff like:
Traceback (most recent call last): File "/usr/share/copr/backend/daemons/worker.py", line 211, in do_job mr.check_build_success() # raises if build didn't succeed File "/usr/share/copr/backend/mockremote/__init__.py", line 313, in check_build_success raise MockRemoteError("Build {} failed".format(self.job)) backend.exceptions.MockRemoteError: Build BuildJob<id: 846392, owner: @copr, project: TEST1568825239Project1, project_dir: TEST1568825239Project1git branch: None, git hash: None, status: 3 > failed During handling of the above exception, another exception occurred: Traceback (most recent call last): File "/usr/share/copr/backend/mockremote/__init__.py", line 317, in download_results self.builder.download_results(self.job.results_dir) File "/usr/share/copr/backend/mockremote/builder.py", line 163, in download_results self.rsync_call(self.resultdir, target_path) File "/usr/share/copr/backend/mockremote/builder.py", line 160, in rsync_call raise BuilderError(err_msg) backend.exceptions.BuilderError: Failed to download data from builder due to rsync error, see the rsync log file for details.
into the worker.log.
The error handling was simplified in 7ef816a
These kinds of tracebacks should not happen.
Metadata Update from @praiskup: - Issue close_status updated to: Fixed - Issue status updated to: Closed (was: Open)
Login to comment on this ticket.