Iss2189 - Remove inttests that have been replaced by an IVT #224
Conversation
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
Signed-off-by: Jade Carino <[email protected]>
eamansour
approved these changes
Apr 4, 2025
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.
Why?
Part of story galasa-dev/projectmanagement#2189
I have set up a new CronJob on cicsk8s that runs the CICSTSManagerIVT, CEMTManagerIVT, CedaManagerIVT, Zos3270IVT, ZosManagerIVT and ZosManagerTSOCommandIVT on prod1 daily at 6am. This is the equivalent of the tests I have removed from the schedule by commenting out their
@Testannotations (the only difference is these tests spin up a "local Galasa ecosystem" on a Linux VM and run the IVT there, instead of directly on prod1).I have removed these tests from the schedule on the regression-run to 1) reduce the load on the Linux VMs 2) reduce the number of tests using the old mechanism, to hopefully reduce the likelihood of tests getting stuck and holding up the whole regression-run.
For the same reasons, I have also removed the tests for the CoreManagerIVT, ArtifactManagerIVT and HttpManagerIVT, as these have been running successfully on ecosystem1.