The status page https://status.fedoraproject.org/ says that COPR is fine. My jobs all say "starting" (for like 12 hours now).
https://download.copr.fedorainfracloud.org/results/barsnick/fed-newer/fedora-34-ppc64le/01966771-bindfs/backend.log
[2021-02-15 15:02:43,863][ INFO][PID:2934804] Marking build as starting [2021-02-15 15:02:43,933][ INFO][PID:2934804] Trying to allocate VM
@praiskup I am expecting it is similar to the armhfp problem, but not sure.
Currently armhfp and ppc64le are built via emulation so are not directly monitored.
Metadata Update from @smooge: - Issue tagged with: aws, copr, medium-gain, medium-trouble, ops
Metadata Update from @smooge: - Issue priority set to: Waiting on External (was: Needs Review)
Meh, sorry, I seem I mistakenly enabled ppc64le chroots for F34. We still expect that we will have the native builders there - so that's we don't want to mixup with emulation.
IOW, there are no builders that support ppc64le architecture builds, so resalloc is starving...
resalloc
I disabled the (only) ppc64le chroot (fedora-34-ppc64le) for now.
I will add this into https://pagure.io/fedora-infrastructure/issue/9059 and consider this closed as fixed
Metadata Update from @smooge: - Issue close_status updated to: Fixed - Issue status updated to: Closed (was: Open)
Issue status updated to: Open (was: Closed)
Issue status updated to: Closed (was: Open) Issue close_status updated to: Fixed
Login to comment on this ticket.