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: decrease job timeout from 6 hours to 30 minutes #7917

Merged
merged 1 commit into from
Oct 21, 2020

Conversation

bluetech
Copy link
Member

We don't have any jobs that should go beyond that, so let's be nicer to
the CI host and quicker to report the failure.

We don't have any jobs that should go beyond that, so let's be nicer to
the CI host and quicker to report the failure.
@bluetech
Copy link
Member Author

main / build (ubuntu-py37) (pull_request) Cancelled after 30m — build (ubuntu-py37)

So it it seems to have worked :)

Copy link
Member

@nicoddemus nicoddemus left a comment

Choose a reason for hiding this comment

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

Thanks for tackling this @bluetech!

@nicoddemus nicoddemus merged commit 824e9cf into pytest-dev:master Oct 21, 2020
@nicoddemus nicoddemus added the needs backport applied to PRs, indicates that it should be ported to the current bug-fix branch label Oct 21, 2020
@nicoddemus
Copy link
Member

Although not happening in previous versions, I think it is worthwhile to backport it anyway.

nicoddemus added a commit to nicoddemus/pytest that referenced this pull request Oct 21, 2020
ci: decrease job timeout from 6 hours to 30 minutes
@nicoddemus
Copy link
Member

Backport: #7919

@nicoddemus nicoddemus added backported and removed needs backport applied to PRs, indicates that it should be ported to the current bug-fix branch labels Oct 21, 2020
@bluetech bluetech deleted the ci-timeout branch November 6, 2020 21:05
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants