562 2010-12-02 07:21:06 +0000 Enhance sanity tests such that 'invasive' tests aren't run with each bitbake invocation 2011-01-14 17:54:40 +0000 1 1 7 Build System, Metadata & Runtime Meta-yocto meta-yocto 1.0 x86 Multiple VERIFIED FIXED Medium normal 1.0 M3 1 josh bluelightning ke.yu kevin.tian poky.bs.watcher poky.watcher richard.purdie sgw --- --- Program Management --- oldest_to_newest 10987 0 josh 2010-12-02 07:21:06 +0000 We are accruing a set of increasingly invasive sanity tests, and would like to add more (such as compiler sanity checks). The simplest way to do this would be to have 2 classes of sanity check. 1) sanity tests which are only run when a SANITY_VERSION number is changed (such as when new tests are added) and 2) sanity tests which are run for each bitbake invocation However it could be more desirable to handle several classes of sanity tests: * ones which are only run 'once' on first use, then possibly again when the SANITY_VERSION is changed (compiler checks, etc). * ones which are only run when one of the directories is moved (tmp, sstate-cache) such as Paul's proposed test for long filenames. * the rest, run with each invocation of bitbake 11243 1 bluelightning 2010-12-20 03:07:31 +0000 Patches have been sent to the mailing list for this one: https://lists.yoctoproject.org/pipermail/poky/2010-December/001375.html 11245 2 bluelightning 2010-12-20 08:03:19 +0000 Patches now merged into master. 11370 3 josh 2011-01-04 07:13:07 +0000 This has indeed been fixed 11484 4 sgw 2011-01-14 17:54:40 +0000 http://git.pokylinux.org/cgit/cgit.cgi/poky/commit/?id=1993ca1f8790ff5bddc347ff22c78fd1c618739a