As part of the work i did for https://issues.apache.org/jira/browse/CASSANDRA-14134, one of the things I did was add a new command line argument “--execute-upgrade-tests”.
all the upgrade tests are now annotated with an upgrade_test pytest annotation. by default they aren’t run. adding a single flag (easily discoverable in the —help) will turn them on if necessary. or you can use the power features of pytest collection filtering when invoking pytest directly (look at the -m option). hope this helps going forward!! best, kjellman On Dec 8, 2017, at 2:03 PM, Michael Shuler <[email protected]<mailto:[email protected]>> wrote: Yep, that rm is a bit of a hack, since environment vars for JDK{8,9}_HOME are not able to be set on the static slaves. The "proper" way to skip them is just a normal nose exclude (drop --collect-only to actually run 'em): ./run_dtests.py --nose-options="--collect-only -e upgrade_tests/" or nosetests --collect-only -e upgrade_tests/ Also, to run only the upgrade_tests, since we're here :) ./run_dtests.py --nose-options="--collect-only upgrade_tests/" or nosetests --collect-only upgrade_tests/ -- Michael On 12/08/2017 12:07 PM, Jay Zhuang wrote: Here is how cassandra-builds jenkins job do:$ rm -r upgrade_tests/ https://github.com/apache/cassandra-builds/blob/master/build-scripts/cassandra-dtest.sh#L50 On Friday, December 8, 2017, 1:28:34 AM PST, Sergey <[email protected]<mailto:[email protected]>> wrote: Hi! How to completely skip upgrade tests when running dtests? Best regards, Sergey --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected]<mailto:[email protected]> For additional commands, e-mail: [email protected]<mailto:[email protected]>
