All the links are 404...
...got deleted. Failed builds are pruned every day, which is too often and will be subject to change.
Related to: Bug 1304695
I think you'll find that there were never any files written unless they're always being removed within seconds of failure.
(In reply to Tom "spot" Callaway from comment #0)
> All the links are 404...
the links are :
shouldn't be copr.fedorainfracloud.org ?
I also have some 404 but on my case , for example:
because the correct is :
url don't have miss my username.
links are correct.
BTW monitor webpage, reports azureus as failed when it was succeeded (other bug)
In reply to Jens Petersen from comment #3)
> I think you'll find that there were never any files written unless they're
> always being removed within seconds of failure.
That is the case for SRPM import failures (into dist-git). If that happens, no directory for build results is even created and the link to the build results should be disabled in UI (so no 404s).
The only way, that I currently know of, to get empty white page from copr-be machine with just 404 error is for the build directory to get deleted by the prunning script.
(In reply to Sergio Monteiro Basto from comment #4)
> (In reply to Tom "spot" Callaway from comment #0)
> > https://copr.fedorainfracloud.org/coprs/spot/chromium/build/156327/
> > All the links are 404...
> the links are :
> shouldn't be copr.fedorainfracloud.org ?
No, the build results are stored on a separate copr-be machine.
> I also have some 404 but on my case , for example:
> this link
> gives 404
> because the correct is :
> url don't have miss my username.
This is a separate issue. It has been fixed by fce4438bba.
> in https://copr.fedorainfracloud.org/coprs/sergiomb/buildsforF21/monitor/
> links are correct.
> BTW monitor webpage, reports azureus as failed when it was succeeded (other
Please, look into the list of COPR bugs and report this one if it has not been reported yet.
Fixed by a5c93116e2.
*** Bug 1304695 has been marked as a duplicate of this bug. ***
*** Bug 1306183 has been marked as a duplicate of this bug. ***
Code with this fix is currently deployed on testing server.
You can test it before it will be deployed to production.
Please see: http://copr-fe-dev.cloud.fedoraproject.org
Copr production machines were upgraded to version containing a fix to this issue.
If you are not satisfied with provided solution, please feel free to reopen this.