Skip to content

Give pypy jobs a 15m timeout (was 9m)#2376

Merged
webknjaz merged 1 commit intojazzband:mainfrom
sirosen:give-pypy-jobs-more-time
Apr 15, 2026
Merged

Give pypy jobs a 15m timeout (was 9m)#2376
webknjaz merged 1 commit intojazzband:mainfrom
sirosen:give-pypy-jobs-more-time

Conversation

@sirosen
Copy link
Copy Markdown
Member

@sirosen sirosen commented Apr 15, 2026

Trivial CI tweak, so I've dropped the template. No changelog for this.

@sirosen sirosen requested a review from a team as a code owner April 15, 2026 16:56
@sirosen sirosen mentioned this pull request Apr 15, 2026
4 tasks
@webknjaz webknjaz enabled auto-merge April 15, 2026 17:02
Copy link
Copy Markdown
Member

@webknjaz webknjaz left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Personally, I like tighter timeouts but this is fine I guess..

@webknjaz webknjaz added this pull request to the merge queue Apr 15, 2026
Merged via the queue into jazzband:main with commit 6be966f Apr 15, 2026
75 checks passed
@sirosen
Copy link
Copy Markdown
Member Author

sirosen commented Apr 15, 2026

I like the timeout to be close to the projected real runtime, but I think that the harm of going too low is worse, in this case, than the harm of going a bit too high.

We can ratchet it tighter in the future, but I value our human time on the project very highly. If we have to re-run CI even a few times in a week, those delays add up.

Probably the best way to decide these things is to script out harvesting runtime data from past runs. I may try my hand at this sometime.

@sirosen sirosen deleted the give-pypy-jobs-more-time branch April 15, 2026 18:34
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants