[patch] Increase FVT step timeout from 90m to 150m #120
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
durera
approved these changes
Dec 21, 2022
durera
changed the title
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.
We have test tasks running for more than 90 minutes. Different from problems in Manage identified before (see this), these tasks are really running and interrupted in the middle of execution. If this new time was not enough, team will need to refactor and break tests in smaller pieces, as they will not fit into a layer 3 pipeline as they are. Follow problems identified today (they are breaking fvt pipeline):
fvt88x(Predict): https://ibm-watson-iot.slack.com/archives/C031Q7W21FZ/p1671558295453799fvtrelease(Predict and Assist): https://ibm-watson-iot.slack.com/archives/C031Q7W21FZ/p1671604376339169