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: do not artificially restrict parallel test execution #745

Merged
merged 1 commit into from
Mar 15, 2024

Conversation

hendriktews
Copy link
Collaborator

For whatever reason, the test job always runs late in a CI run (I am blaming the max-parallel annotation for this). This leads to longer CI runs, because, at the end, for several rounds on 6 instances of the test job are executing. Note that Github starts at most 20 of our tests in parallel, so it is not our responsibility to ensure that limit.

For whatever reason, the test job always runs late in a CI run (I am
blaming the max-parallel annotation for this). This leads to longer CI
runs, because, at the end, for several rounds on 6 instances of the
test job are executing. Note that Github starts at most 20 of our
tests in parallel, so it is not our responsibility to ensure that
limit.
Copy link
Member

@erikmd erikmd left a comment

Choose a reason for hiding this comment

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

Thanks @hendriktews ! indeed I don't see any drawback to raise the max number of these parallel jobs.

@hendriktews hendriktews merged commit 728bd25 into ProofGeneral:master Mar 15, 2024
119 checks passed
@hendriktews hendriktews deleted the no-max branch March 15, 2024 20:14
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