[Refactor] Use RAYCLUSTER_DEFAULT_REQUEUE_SECONDS_ENV as timeout of status check in tests #1755
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.
As @kevin85421 found out, we have set
RAYCLUSTER_DEFAULT_REQUEUE_SECONDS_ENV
to 10 seconds to speed up the tests. But we still wait forutils.RAYCLUSTER_DEFAULT_REQUEUE_SECONDS+5
, which is 305 seconds and is too long, to fail a test.I believe this inconsistency exists because there is no convenient converter for the env variable.
In this PR, I replaced all usages of
RAYCLUSTER_DEFAULT_REQUEUE_SECONDS
withRAYCLUSTER_DEFAULT_REQUEUE_SECONDS_ENV
in tests with the help of a simpleMustGetEnvInt
converter.This change can fail our tests faster if any unexpected occurs.
Checks