11847 2017-07-27 16:08:00 +0000 Add an option to oe-selftest to run all tests except for [...] 2017-08-16 19:41:11 +0000 1 1 10 QA/Testing Build Testing general 2.4 x86 Multiple RESOLVED FIXED Medium+ enhancement 2.4 M3 11848 1 joshuagloe leonardo.sandoval.gonzalez anibal.limon leonardo.sandoval.gonzalez --- --- Don't know oldest_to_newest 75352 0 joshuagloe 2017-07-27 16:08:00 +0000 It would be great if we could run all oe-selftest tests barring those specified as an option. Something like: oe-selftest -R distrodata We'd like this because the distrodata selftests are prone to transient failures due to networking issues. We'd like to run these separately on the autobuilder with a lower BB_NUMBER_THREADS, likely even less frequently (automated once per week). If we do so we'd also remove the distrodata.Distrodata.test_checkpkg test from the nightly-oe-selftest builder, but there's no easy way to run all tests except that one. Maintaining a list of tests we do want to run for the nightly-oe-selftest buildset is prone to bitrotting and missing out on valuable testing. 75610 1 leonardo.sandoval.gonzalez 2017-08-03 14:02:44 +0000 For some reason, I needed to send the patch a second time and this time it arrived to the ML http://lists.openembedded.org/pipermail/openembedded-core/2017-August/140441.html 75702 2 anibal.limon 2017-08-07 21:47:10 +0000 (In reply to comment #0) > It would be great if we could run all oe-selftest tests barring those > specified as an option. Something like: > > oe-selftest -R distrodata > > We'd like this because the distrodata selftests are prone to transient > failures due to networking issues. We'd like to run these separately on the > autobuilder with a lower BB_NUMBER_THREADS, likely even less frequently > (automated once per week). > > If we do so we'd also remove the distrodata.Distrodata.test_checkpkg test > from the nightly-oe-selftest builder, but there's no easy way to run all > tests except that one. > > Maintaining a list of tests we do want to run for the nightly-oe-selftest > buildset is prone to bitrotting and missing out on valuable testing. The option is good to have it, for a quick fix you can avoid run distrodata tests moving the module to starts with _ (_distrodata), this will avoid to run the test module when request --run-all-tests. Anibal 75922 3 leonardo.sandoval.gonzalez 2017-08-16 19:41:11 +0000 merged at master: e40eeaa790: Leonardo Sandoval: Fri Aug 11 00:08:31 2017 +0100: context: Include a command line argument to run all except certain tests