Skip to content
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.

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

CI: Bump azure pipeline timeout to 120 minutes #25582

Merged
merged 1 commit into from
Jan 14, 2024

Conversation

seberg
Copy link
Member

@seberg seberg commented Jan 14, 2024

Not sure if this will work, but maybe the default of 60minutes is just suddenly (correctly?) enforced. I didn't see any note that it changed with a quick google.

Closes gh-25577

Not sure if this will work, but maybe the default of 60minutes is
just suddenly (correctly?) enforced.  I didn't see any note that
it changed with a quick google.
@seberg
Copy link
Member Author

seberg commented Jan 14, 2024

OK, I think there is a decent change it's going to work, because the current setting has: TimeoutInMinutes: 60. But I also think we need to merge it for the change to take effect.

EDIT: Oooops, no the timeout is already set to 120 minutes, so lets see. I was looking at the lint step, which this didn't change of course.

@charris charris merged commit b0371ef into numpy:main Jan 14, 2024
64 checks passed
@charris
Copy link
Member

charris commented Jan 14, 2024

Thanks Sebastian.

@charris charris removed the 09 - Backport-Candidate PRs tagged should be backported label Jan 14, 2024
@seberg seberg deleted the azure-timeout branch January 14, 2024 22:03
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.

CI: Azure jobs are aborting after running for 60 minutes
2 participants