Bug 562 - Enhance sanity tests such that 'invasive' tests aren't run with each bitbake invocation
Summary: Enhance sanity tests such that 'invasive' tests aren't run with each bitbake ...
Status: VERIFIED FIXED
Alias: None
Product: Meta-yocto
Classification: Build System, Metadata & Runtime
Component: meta-yocto (show other bugs)
Version: 1.0
Hardware: x86 Multiple
: Medium normal
Target Milestone: 1.0 M3
Assignee: Paul Eggleton
QA Contact:
URL:
Whiteboard:
Depends on:
Blocks:
 
Reported: 2010-12-02 07:21 UTC by Joshua Lock - Disabled
Modified: 2011-01-14 17:54 UTC (History)
6 users (show)

See Also:
OS type for building Yocto: ---
Type of Regression: ---
Verified: Program Management
Documentation change: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Joshua Lock - Disabled 2010-12-02 07:21:06 UTC 
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
Comment 1 Paul Eggleton 2010-12-20 03:07:31 UTC 
Patches have been sent to the mailing list for this one:
https://lists.yoctoproject.org/pipermail/poky/2010-December/001375.html
Comment 2 Paul Eggleton 2010-12-20 08:03:19 UTC 
Patches now merged into master.
Comment 3 Joshua Lock - Disabled 2011-01-04 07:13:07 UTC 
This has indeed been fixed