Custom source timeout?

[qoijjj]

For @secureblue/hardened-chromium, the source extraction and cleaning for the underlying chromium takes between 58 minutes and 62 minutes on the COPR source builder.

Since the source build timeout is 60 minutes, this means that 1 out of every 3 or 4 source builds gets timed out. Is there any way we can increase this to say 90 minutes? I see there's a field for build timeout customization, but not for source timeout.

Making this change would result in less copr builder usage by @secureblue/hardened-chromium since we wouldn't need to retry those timed-out builds.

[FrostyX]

Thank you for the report @qoijjj,

Is there any way we can increase this to say 90 minutes?

I don't think there is any.

I would go the easiest route and globally increase the limit from 60 minutes to 90 minutes instead of implementing a SRPM build timeout option. We will discuss it on a Monday meeting.

[qoijjj]

@FrostyX That would be great. What was the verdict from the meeting?

[FrostyX]

The verdict was, that we are going to increase the timeout to 90 minutes since that's the simplest solution for all of us.
I'll take a look at it this week.

[FrostyX]

@qoijjj the PR with the fix was merged but you'll need to wait until it gets to production. The new release wasn't scheduled yet, so it will take something from two weeks to a month.

Since it is a trivial fix, I'd hotfix it in production so that you would have it there instantly but unfortunately, the change was in a component that is hard to hotfix, and a proper release is required.

[qoijjj]

@FrostyX no problem, thanks for increasing it!