| Summary: | oe-selftest: Use SSTATES without corrupting them. | ||
|---|---|---|---|
| Product: | [QA/Testing] Build Testing | Reporter: | Mariano Lopez <mariano.lopez> |
| Component: | general | Assignee: | Leonardo Sandoval Gonzalez <leonardo.sandoval.gonzalez> |
| Status: | VERIFIED DUPLICATE | QA Contact: | Jose Perez C <jose.perez.carranza> |
| Severity: | enhancement | ||
| Priority: | High | CC: | benjamin.esquivel, joshuagloe, juan.fernandox.ramos.frayle, leonardo.sandoval.gonzalez, richard.purdie, sgw |
| Version: | unspecified | ||
| Target Milestone: | 2.3 M3 | ||
| Hardware: | x86 | ||
| OS: | Multiple | ||
| Whiteboard: | |||
| OS type for building Yocto: | --- | Type of Regression: | New (Never tested) |
| Verified: | Documentation change: | Don't know | |
| Bug Depends on: | 10929, 10937 | ||
| Bug Blocks: | |||
|
Description
Mariano Lopez
2016-07-26 21:02:26 UTC
Due to time constrains, moving it to next enhancement window. I would like to see how the SSTATES get corrupted, how can I check this out? I have never actually seen this. I opened the bug because I was told that this was the reason for selftest not using SSTATES, I don't remember who said that. (In reply to comment #3) > I have never actually seen this. I opened the bug because I was told that > this was the reason for selftest not using SSTATES, I don't remember who > said that. Mariano, I believe 'corrupted' means that the shared states are touched by the selftests thus effectively changing the state. (In reply to comment #4) > > Mariano, I believe 'corrupted' means that the shared states are touched by > the selftests thus effectively changing the state. This bug was filed as a result of a comment from RP and we've already discussed what corrupted means and it doesn't look like corrupted = changed in this case. Corrupted here means that sstate gets deleted. Nothing on the autobuilder should run a "-c cleansstate". The issue is that a build can be part way through running having checked sstate exists, then it can find it no longer does whilst its trying to use it. We could just use the sstate as a read only mirror for oe-selftest to ensure that it can't delete things. Where a test needs to run an sstate clean, it could use "-f" to force a taint to a hash instead? (In reply to comment #7) > We could just use the sstate as a read only mirror for oe-selftest to ensure > that it can't delete things. Where a test needs to run an sstate clean, it > could use "-f" to force a taint to a hash instead? thanks for the clarification Richard. Mariano, this looks like a way to start the investigation on this bug. Assigning it to Leo whom will try to get it done for M1. The is a newer bug (10929), filed by RP reporting an symptom of the main problem. Benjamin did some work on 10929 thus is more advance that this one. Making this as duplicated of 10929. *** This bug has been marked as a duplicate of bug 10929 *** Verified, tested with commit b6a1004c73820cff833f2b6f09d2432706f5447a, no SSTATES were corrupted after selftest |