We want to get core dumps from these builders in order to try and track
down livemedia failures in python with SIGILL.
https://bugzilla.redhat.com/show_bug.cgi?id=2247319
We just enable this on those builders for now and we set it so it is the
limit for the systemd-nspawn containers that mock uses.
Signed-off-by: Kevin Fenzi <kevin@scrye.com>
f39 adds flatpaks for ppc64le, so we need to allow ppc64le builders to
access the registry directly so they can install flatpaks in the ostree
install images. Without this they try and get them from the cdn and the
builder firewall blocks them and it times out and the image fails to
compose.
Signed-off-by: Kevin Fenzi <kevin@scrye.com>
We aren't using this box and there's a use for it in the CentOS side, so
we are going to hand it over there. :)
Signed-off-by: Kevin Fenzi <kevin@scrye.com>
It's overall simpler and more idempotent to just use a side repo
maintained outside of ansible than re-create one on each system
on each run of the plays.
Signed-off-by: Adam Williamson <awilliam@redhat.com>
This still doesn't mean that one project (= sandbox) can waste that
many workers, we still keep the per/sandbox limit on 35. This change
though drastically helps Packit which serves many users under a single
owner (but multiple sandboxes).
The pattern matching allows me to do tests in projects like:
$ copr-dev create measure-aws-powerful-c7i.8xlarge --chroot fedora-rawhide-x86_64
But the instance type needs to be selected manually in pools.yaml.
This will recycle VMs more quickly, after 90s of idling. This is giving
their assigned users smaller changes to re-take it. This though should
not be a problem nowadays since copr-backend is pretty optimal and each
"task dispatching cycle" takes less than 30s. If users have multiple
tasks to process, these tasks should still be happily dispatched within
the time-frame.
Rocky was added in the Anitya GUI, but does not have a mapping, so links
are not created for them which point to their corresponding sources on
their git forge.
