Hi,

I've updated the global timeout to 1 hour and specifically for the glibc package to
2 hours [1]. If needed we can increase it, in that case let me know or feel free to send
a merge request to update the CI config.

In any case if you'd like to opt out then the package could be removed from there: [2].

[1]: https://gitlab.com/redhat/centos-stream/ci-cd/zuul/jobs-config/-/merge_requests/6
[2]: https://gitlab.com/redhat/centos-stream/ci-cd/zuul/project-config/-/blob/master/resources/centos-distgits.yaml

On Wed, Jun 23, 2021 at 6:20 AM Fabian Arrotin <arrfab@centos.org> wrote:
On 22/06/2021 21:48, Florian Weimer wrote:
> It seems that these jobs have a hard timeout of 30 minutes.  It is just
> not possible to build the glibc RPM in under 30 minutes on a single
> Haswell-era CPU, so these cycles go to waste because every attempt will
> time out.
>
> Is there a way to opt out of this, to conserve resources?
>
> Thanks,
> Florian
>

Hi Florian,

May I suggest you to instead reach out internally to the OSCI team in
charge of this ?
I doubt that the team members responsible for the Zuul infra for Stream
9 are subscribed/following closely theads on the centos-devel list, and
so to ensure that your request is seen/been tracked, it would be better
to create Jira ticket in the dedicated Stream project there and have it
assigned to the correct team ;-)


--
Fabian Arrotin
The CentOS Project | https://www.centos.org
gpg key: 17F3B7A1 | twitter: @arrfab

_______________________________________________
CentOS-devel mailing list
CentOS-devel@centos.org
https://lists.centos.org/mailman/listinfo/centos-devel