Description of problem: Sometimes, after building the source package without error, the build stops unexpectedly. Version-Release number of selected component (if applicable): How reproducible: I have no idea how to reproduce, it is intermittent. Actual results: https://copr-be.cloud.fedoraproject.org/results/duck/osas-infra-team-rpm-repo/fedora-26-i386/00592926-postsrsd/build.log.gz https://copr-be.cloud.fedoraproject.org/results/duck/osas-infra-team-rpm-repo/fedora-26-ppc64le/00592724-postsrsd/build.log.gz Expected results: Build should go on. Additional info: Retrying the build works fine, so it's not a blocker, just annoying. The log do not show any error, so it must be ignored/hidden.
Hello, here the error is in https://copr-be.cloud.fedoraproject.org/results/duck/osas-infra-team-rpm-repo/fedora-26-i386/00592926-postsrsd/root.log.gz during package download. I will keep this open as there perhaps is something we can do about is if the problem do not disappear.
Ho, I did not see this, thanks for investigating. So if 6 mirrors fail with 404, then maybe there's a problem with the way they are updated. We might reassign this ticket to people in charge of the mirrors then.
Right but problems with mirrors occur occasionally. If too often than this should really be reported against Fedora Infra issue tracker (https://pagure.io/fedora-infrastructure).
The mirrors seem quite stable at the moment so I think this can be closed.
I just made a build and got a mirror failure on one arch: https://copr-be.cloud.fedoraproject.org/results/duck/osas-infra-team-rpm-repo/epel-7-x86_64/00738754-needrestart/builder-live.log
I sent an email to copr-devel to find out if there are more users hitting this issue. We will see about it. The only thing we could here is to setup our own stable mirror but it will take some time so first we could fix the issues on infra level.
We have fixed the issue. The problem was on Fedora mirrors.
thanks a lot