10929 2017-01-16 14:11:42 +0000 oe-selftest corrupts sstate cache 2017-06-14 21:23:40 +0000 1 1 10 QA/Testing Build Testing general unspecified x86 Multiple VERIFIED FIXED High major 2.3 M3 10035 10874 1 richard.purdie mariano.lopez benjamin.esquivel joshuagloe juan.fernandox.ramos.frayle leonardo.sandoval.gonzalez mariano.lopez jose.perez.carranza --- --- No (bug/feature does not impact docs) oldest_to_newest 69825 0 richard.purdie 2017-01-16 14:11:42 +0000 If you run oe-selftest, then try to "bitbake core-image-sato -c populate_sdk_ext", it fails with unexpected setscene execution errors. This is because things get cleaned from the sstate cache by oe-selftest but the stamp files are left meaning the eSDK can't find the sstate files, leading to obtuse build failures. The appoximate list of broken (removed) sstate is: groff-native openssl cross-localedef-native db glibc-locale cryptodev-linux ptest-runner base-files libffi sqlite3 ncurses expat opkg-utils bzip2 69826 1 leonardo.sandoval.gonzalez 2017-01-16 16:14:58 +0000 this is a more general bug 10035. However, lets not mark this as duplicated because the latter needs to be divided into several ones, like this one. 69918 2 benjamin.esquivel 2017-01-18 23:57:27 +0000 I am re-routing this issue to the main triage. 69975 3 benjamin.esquivel 2017-01-20 19:58:25 +0000 I can't seem to reproduce this issue, I will post my procedure here: 1. clone poky 2. init build environment (non memres) 3. execute a selftest --run-all-tests 4. execute a bitbake core-image-sato -c populate_sdk_ext 5. expect failure I assume that the sstates that will get corrupted thus 5 would fail are the ones located at the build/sstate-cache but this is the point where my procedure might be wrong to reproduce the issue. RP, what am I missing? 70005 4 richard.purdie 2017-01-23 14:44:42 +0000 (In reply to comment #3) > I can't seem to reproduce this issue, I will post my procedure here: > > 1. clone poky > 2. init build environment (non memres) > 3. execute a selftest --run-all-tests > 4. execute a bitbake core-image-sato -c populate_sdk_ext > 5. expect failure > > I assume that the sstates that will get corrupted thus 5 would fail are the > ones located at the build/sstate-cache but this is the point where my > procedure might be wrong to reproduce the issue. RP, what am I missing? You're missing a "bitbake core-image-sato -c populate_sdk_ext" before running selftest. 70008 5 benjamin.esquivel 2017-01-23 14:52:32 +0000 (In reply to comment #4) > (In reply to comment #3) > > I can't seem to reproduce this issue, I will post my procedure here: > > > > 1. clone poky > > 2. init build environment (non memres) > > 3. execute a selftest --run-all-tests > > 4. execute a bitbake core-image-sato -c populate_sdk_ext > > 5. expect failure > > > > I assume that the sstates that will get corrupted thus 5 would fail are the > > ones located at the build/sstate-cache but this is the point where my > > procedure might be wrong to reproduce the issue. RP, what am I missing? > > You're missing a "bitbake core-image-sato -c populate_sdk_ext" before > running selftest. thanks, retrying. 70055 6 3601 benjamin.esquivel 2017-01-23 21:50:55 +0000 Created attachment 3601 find-10929.sh I wrote this script and ran it on an opensuse system and did not show failures at the populate_sdk_ext task. I am running it on a fedora system but I suspect this can be seen at the autobuilder with more clarity so I'll try to run the test there as well. 70085 7 leonardo.sandoval.gonzalez 2017-01-24 16:25:20 +0000 *** Bug 10035 has been marked as a duplicate of this bug. *** 70336 8 mariano.lopez 2017-02-01 15:51:14 +0000 After a conversation with Benjamin and Richard, the problem is as follows: 1. Start simultaneous builds along with selftest. 2. One of the builds will check for share states for X recipe. 3. Build found share states for X recipe. 4. selftest runs cleansstate task on recipe X. 5. Build tries to fetch share states for X recipe and fails. So, the only way to do this is to avoid using cleansstate in selftest, it is needed to check for this task in selftest's tests and change all of them for something that perform the required test without deleting sstate. 70595 9 mariano.lopez 2017-02-09 16:32:15 +0000 Sent patch to the mailing list: https://patchwork.openembedded.org/series/5239/# 71045 10 mariano.lopez 2017-03-02 16:12:47 +0000 This has been solved in commit: http://cgit.openembedded.org/openembedded-core/commit/?id=62c61087a10cc3b26fbff32c9e2efd1704a39724 74172 11 juan.fernandox.ramos.frayle 2017-06-14 21:23:40 +0000 Verified, tested with commit b6a1004c73820cff833f2b6f09d2432706f5447a, no SSTATES were corrupted after selftest 3601 2017-01-23 21:50:55 +0000 2017-01-23 21:50:55 +0000 find-10929.sh file_10929.txt text/plain 409 benjamin.esquivel IyEvYmluL2Jhc2gNCg0KdGltZXN0YW1wPWBkYXRlICslWSVtJWQtJUglTWANCnRtcGRpcj1idWcx MDkyOS0kdGltZXN0YW1wDQoNCmdpdCBjbG9uZSBnaXQ6Ly9naXQueW9jdG9wcm9qZWN0Lm9yZy9w b2t5ICR0bXBkaXINCg0KcHVzaGQgJHRtcGRpcg0KLiAuL29lLWluaXQtYnVpbGQtZW52DQpiaXRi YWtlLWxheWVycyBhZGQtbGF5ZXJzIC4uL21ldGEtc2VsZnRlc3QNCmJpdGJha2UgY29yZS1pbWFn ZS1zYXRvIC1jIHBvcHVsYXRlX3Nka19leHQNCm9lLXNlbGZ0ZXN0IC0tcnVuLWFsbC10ZXN0cw0K Yml0YmFrZSBjb3JlLWltYWdlLXNhdG8gLWMgcG9wdWxhdGVfc2RrX2V4dA0KIyB0aGlzIGlzIHdo ZXJlIHRoZSBmYWlsdXJlIHNob3VsZCBvY2N1ciBtZW50aW9uaW5nIHRoZSBjb3JydXB0ZWQgc3N0 YXRlcw0KcG9wZA==