Skip to content

[CI] 3 hour timeout is not enough #58480

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Closed
Disasm opened this issue Feb 15, 2019 · 1 comment
Closed

[CI] 3 hour timeout is not enough #58480

Disasm opened this issue Feb 15, 2019 · 1 comment
Labels
T-infra Relevant to the infrastructure team, which will review and decide on the PR/issue.

Comments

@Disasm
Copy link
Contributor

Disasm commented Feb 15, 2019

There was only one successful build in the last 24 hours: #58446 (comment)
All other builds were failed with timeout either on Travis or AppVeyor.

Related: #58160
@jonas-schievink jonas-schievink added the T-infra Relevant to the infrastructure team, which will review and decide on the PR/issue. label Feb 15, 2019
@pietroalbini
Copy link
Member

The infra team already discussed this in the past, and our consensus is to keep the timeout to 3 hours. Our CI builds already take too long, limiting the amount of PRs we can merge in a day even if each of them doesn't fail. We prefer to work torwards reducing the amount of time spent on CI, and the timeout is an incentive to do so.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
T-infra Relevant to the infrastructure team, which will review and decide on the PR/issue.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@Disasm @jonas-schievink @pietroalbini