[patch] Increase MAX_RETRIES for launchfvt-predict from 50 to 72 - #2530
Merged
Conversation
The predict FVT suite executes long-running Watson Studio notebook jobs and routinely takes well over 4 hours to complete. The wait-for-pipelinerun step in mas-launchfvt-predict was configured with MAX_RETRIES=50 (50 x 5 min = 4h 10m), which is shorter than both the 6h step timeout and the 8h pipeline timeout set on the predict PipelineRun itself. When the watcher exhausted its retries while predict was still running, IGNORE_FAILURE=True caused the step to exit 0, making the launcher believe predict had finished. This triggered the mas-fvt-finally pipeline (deprovision, must-gather) while predict tests were still actively executing, cutting the suite short. Increase MAX_RETRIES to 72 (72 x 5 min = 6h), aligning the launcher's watch window with the 6h step timeout on the fvt-predict task so the watcher does not give up before the tests can legitimately complete. Root-cause reference: build 8295, instance pfvtjdmnp92, 2026-08-14.
unnati-solanki-git
approved these changes
Aug 14, 2026
This file contains hidden or 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 join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
The predict FVT suite executes long-running Watson Studio notebook jobs and routinely takes well over 4 hours to complete. The wait-for-pipelinerun step in mas-launchfvt-predict was configured with MAX_RETRIES=50 (50 x 5 min = 4h 10m), which is shorter than both the 6h step timeout and the 8h pipeline timeout set on the predict PipelineRun itself.
When the watcher exhausted its retries while predict was still running, IGNORE_FAILURE=True caused the step to exit 0, making the launcher believe predict had finished. This triggered the mas-fvt-finally pipeline (deprovision, must-gather) while predict tests were still actively executing, cutting the suite short.
Increase MAX_RETRIES to 72 (72 x 5 min = 6h), aligning the launcher's watch window with the 6h step timeout on the fvt-predict task so the watcher does not give up before the tests can legitimately complete.
Root-cause reference: build 8295, instance pfvtjdmnp92, 2026-08-14.
FVT Dashboard :https://dashboard.ibmmas.com/tests/pfvtjdmnp92/8295