This repository has been archived by the owner on Aug 2, 2022. It is now read-only.
new timeout to handle when two jobs on the same host are maxing their… #7995
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Change Description
When two unit tests run on the same host, they max their CPU usage and slow down enough that they both hit the 45 minute timeout.
https://buildkite.com/EOSIO/eosio/builds/17836#056319ae-5c35-46f9-81e8-ce15683bfdf4
https://buildkite.com/EOSIO/eosio/builds/17829#be7a6232-3b3f-4c73-a336-ba9fbdfd57e2
Needs to be 60 minutes.
Consensus Changes
API Changes
Documentation Additions