Minor changes to integtests #148
Merged
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
added 5 commits
November 4, 2024 14:16
…systemtest_integtest_bundle.sh script when we run an integtest from the base release.
…r tests to the integtest README file.
… in the minimal_system_quick_test from 72 to 128 since we expect all TC fragments produced by the RandomTCMakerModule to be non-empty.
…ple_system_test.py
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.
This PR has four small changes:
integtest/README.mdfile was updated to include a hint about thepytest"-k" option and to describe more of the available tests-p no:cacheprovideroption was added to thepytestcommand in the bundle script when it calls the test from the base releasesmall_footprint_quick_testandexample_system_testwere added to the bundle scriptminimal_system_quick_testsince we expect non-empty TC fragments when using theRandomTCMakerModuleI was thinking that we should target these changes to the
prep-release/fddaq-v5.2.0branch, but I realized that if we merged them to thedevelopbranch first, we could test theno:cacheproviderchange in the next nightly build before merging them to the prep-release branch....