feat: configure checkpoint and validation periods without steps [DET-3525] #854
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
…eriments can load at least
…to min_valckpt_period_with_steps
|
Closed in favor of #885. |
eecsliu
pushed a commit
to eecsliu/determined
that referenced
this pull request
Jun 23, 2023
…-ai#854) If the synchronous launch takes too long, we may run into a job monitoring poll which will detect the dispatchID as 404/NOT_FOUND and stop monitoring. This would cause status updates to stop and the job to show only QUEUED even though it is executing. Add a launchInProgress flag to the job monitor to cause 404/NOT_FOUND to be ignored until the launch has succeeded to avoid this case.
stoksc
pushed a commit
that referenced
this pull request
Jun 26, 2023
If the synchronous launch takes too long, we may run into a job monitoring poll which will detect the dispatchID as 404/NOT_FOUND and stop monitoring. This would cause status updates to stop and the job to show only QUEUED even though it is executing. Add a launchInProgress flag to the job monitor to cause 404/NOT_FOUND to be ignored until the launch has succeeded to avoid this case.
eecsliu
pushed a commit
that referenced
this pull request
Jun 28, 2023
If the synchronous launch takes too long, we may run into a job monitoring poll which will detect the dispatchID as 404/NOT_FOUND and stop monitoring. This would cause status updates to stop and the job to show only QUEUED even though it is executing. Add a launchInProgress flag to the job monitor to cause 404/NOT_FOUND to be ignored until the launch has succeeded to avoid this case.
eecsliu
pushed a commit
that referenced
this pull request
Jun 28, 2023
If the synchronous launch takes too long, we may run into a job monitoring poll which will detect the dispatchID as 404/NOT_FOUND and stop monitoring. This would cause status updates to stop and the job to show only QUEUED even though it is executing. Add a launchInProgress flag to the job monitor to cause 404/NOT_FOUND to be ignored until the launch has succeeded to avoid this case.
stoksc
pushed a commit
that referenced
this pull request
Jul 20, 2023
If the synchronous launch takes too long, we may run into a job monitoring poll which will detect the dispatchID as 404/NOT_FOUND and stop monitoring. This would cause status updates to stop and the job to show only QUEUED even though it is executing. Add a launchInProgress flag to the job monitor to cause 404/NOT_FOUND to be ignored until the launch has succeeded to avoid this case.
eecsliu
pushed a commit
that referenced
this pull request
Jul 24, 2023
If the synchronous launch takes too long, we may run into a job monitoring poll which will detect the dispatchID as 404/NOT_FOUND and stop monitoring. This would cause status updates to stop and the job to show only QUEUED even though it is executing. Add a launchInProgress flag to the job monitor to cause 404/NOT_FOUND to be ignored until the launch has succeeded to avoid this case.
stoksc
pushed a commit
that referenced
this pull request
Oct 17, 2023
If the synchronous launch takes too long, we may run into a job monitoring poll which will detect the dispatchID as 404/NOT_FOUND and stop monitoring. This would cause status updates to stop and the job to show only QUEUED even though it is executing. Add a launchInProgress flag to the job monitor to cause 404/NOT_FOUND to be ignored until the launch has succeeded to avoid this case.
azhou-determined
pushed a commit
that referenced
this pull request
Dec 7, 2023
If the synchronous launch takes too long, we may run into a job monitoring poll which will detect the dispatchID as 404/NOT_FOUND and stop monitoring. This would cause status updates to stop and the job to show only QUEUED even though it is executing. Add a launchInProgress flag to the job monitor to cause 404/NOT_FOUND to be ignored until the launch has succeeded to avoid this case.
wes-turner
pushed a commit
that referenced
this pull request
Feb 2, 2024
If the synchronous launch takes too long, we may run into a job monitoring poll which will detect the dispatchID as 404/NOT_FOUND and stop monitoring. This would cause status updates to stop and the job to show only QUEUED even though it is executing. Add a launchInProgress flag to the job monitor to cause 404/NOT_FOUND to be ignored until the launch has succeeded to avoid this case.
rb-determined-ai
pushed a commit
that referenced
this pull request
Feb 29, 2024
If the synchronous launch takes too long, we may run into a job monitoring poll which will detect the dispatchID as 404/NOT_FOUND and stop monitoring. This would cause status updates to stop and the job to show only QUEUED even though it is executing. Add a launchInProgress flag to the job monitor to cause 404/NOT_FOUND to be ignored until the launch has succeeded to avoid this case.
amandavialva01
pushed a commit
that referenced
this pull request
Mar 18, 2024
If the synchronous launch takes too long, we may run into a job monitoring poll which will detect the dispatchID as 404/NOT_FOUND and stop monitoring. This would cause status updates to stop and the job to show only QUEUED even though it is executing. Add a launchInProgress flag to the job monitor to cause 404/NOT_FOUND to be ignored until the launch has succeeded to avoid this case.
eecsliu
pushed a commit
that referenced
this pull request
Apr 18, 2024
If the synchronous launch takes too long, we may run into a job monitoring poll which will detect the dispatchID as 404/NOT_FOUND and stop monitoring. This would cause status updates to stop and the job to show only QUEUED even though it is executing. Add a launchInProgress flag to the job monitor to cause 404/NOT_FOUND to be ignored until the launch has succeeded to avoid this case.
eecsliu
pushed a commit
to determined-ai/determined-release-testing
that referenced
this pull request
Apr 22, 2024
…-ai#854) If the synchronous launch takes too long, we may run into a job monitoring poll which will detect the dispatchID as 404/NOT_FOUND and stop monitoring. This would cause status updates to stop and the job to show only QUEUED even though it is executing. Add a launchInProgress flag to the job monitor to cause 404/NOT_FOUND to be ignored until the launch has succeeded to avoid this case.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Description
opening for some ci as I do final tweaks.
Test Plan
Commentary (optional)