linux/poky.git/meta/classes/sstate.bbclass, branch uninative-3.5

sstate: fix up additional debugging when fetch fails occur

2022-02-10T10:32:08+00:00

This should print the actual stack trace, for real :) (From OE-Core rev: 9fbc7d6a2b2388e70a76cb97285e2f60bdc79624) Signed-off-by: Alexander Kanavin Signed-off-by: Richard Purdie

sstate: additional debugging when fetch fails occur

2022-02-08T14:20:18+00:00

Autobuilder has been showing things like: Checking sstate mirror object availability...ERROR: SState: cannot test file://universal/d9/bc/sstate:xz-native:x86_64-linux:5.2.5:r0:x86_64:8:d9bced04b194d5fc8d778eb8a0d674fa7375a42c8c50a9237e6d7672e9e7a00c_deploy_source_date_epoch.tar.zst: TimeoutError('timed out') ERROR: SState: cannot test file://37/a0/sstate:libgcc-initial:core2-64-poky-linux:11.2.0:r0:core2-64:8:37a0a5aec105a0822df098f15ff2b67d0e7220204742b5d2b1f7958dda6fa5ce_deploy_source_date_epoch.tar.zst: TimeoutError('timed out') ERROR: SState: cannot test file://universal/11/a4/sstate:libpciaccess-native:x86_64-linux:0.16:r0:x86_64:8:11a4d6c3a2e147ef7dd5f31c0ff2a91271dad49b561d8aa24849115081cf1842_deploy_source_date_epoch.tar.zst: TimeoutError('timed out') done. which is not helpful. To find out what really happened and where, the original traceback is needed too. (From OE-Core rev: 80a9052221fb2a12e7c652f2d1764101202fdb90) Signed-off-by: Alexander Kanavin Signed-off-by: Richard Purdie

abi_version/sstate: Bump for hash equivalence fix

2022-02-05T12:26:36+00:00

With the hash equivalence fix, we need to bump the sstate and hash equivalence version numbers to ensure older task hashes aren't matched into the new namespace. (From OE-Core rev: 3f229267e0588c747265e849ee19724033cc6a80) Signed-off-by: Richard Purdie

staging: Add extra hash handling code

2022-02-05T12:26:36+00:00

Target build output, stored in do_populate_sysroot or do_package can depend not only upon direct dependencies but also indirect ones. A good example is linux-libc-headers. The toolchain depends on this but most target recipes do not. There are some headers which are not used by the toolchain build and do not change the toolchain task output, hence the task hashes can change without changing the sysroot output of that recipe yet they can influence others. A specific example is rtc.h which can change rtcwake.c in util-linux but is not used in the glibc or gcc build. To account for this, we need to account for the populate_sysroot hashes in the task output hashes. (From OE-Core rev: 1cf62882bbac543960e4815d117ffce0e53bda07) Signed-off-by: Richard Purdie

sstate: A third fix for for touching files inside pseudo

2022-01-26T06:27:00+00:00

This continues where commit676757f "sstate: fix touching files inside pseudo" and commit 29fc8599 "sstate: another fix for touching files inside pseudo" left off. The previous changes switched from trying to check if the sstate file is writable before touching it, to always touching the sstate file and ignoring any errors. However, if the sstate file is actually a symbolic link that links to nothing, this would actually result in an empty sstate file being created. And this in turn leads to that future setscene tasks will fail when they try to unpack the empty file. Change the code so that if an sstate file linking to nothing already exists, it is overwritten with the new sstate file. Also change it so that the temporary file that is used is always removed, even if ln fails to link the sstate file to it. (From OE-Core rev: 552197a0c4c9f75a9177c00b197ea91296ed9fc4) Signed-off-by: Peter Kjellerstedt Signed-off-by: Richard Purdie

sstate: Improve failure to obtain archive message/handling

2022-01-19T23:03:43+00:00

The bb.fatal() case where sstate failed to find/use an archive in setcene tasks is suboptimal. Bitbakes handling of setscene tasks will be to warn but the fatal will turn this into an error, despite the real task being rerun. In these failure cases other messages would usually have been printed so turn this into a warning and raise a handled exception status so that bitbake knows to fail the task but not print more messages. (From OE-Core rev: 7875baeca7a3ed216b2442fb8771e51efbfa5a4f) Signed-off-by: Richard Purdie

sstate: Show better exception information for failures

2022-01-19T23:03:43+00:00

Errors like SState: cannot test file://universal/5f/10/sstate:m4-native:x86_64-linux:1.4.19:r0:x86_64:7:5f108b175274798b17950b5ee686bf61445e90fb204d7f795e5b879b5603e88b_deploy_source_date_epoch.tar.zst: 'GIT_SSL_CAINFO' aren't useful, try and improve on this. (From OE-Core rev: 1701d40536db098adb26508799bae13733f1a6fd) Signed-off-by: Richard Purdie

sstate: Preserve permissions when extracting tar archive

2022-01-15T16:23:24+00:00

This is done by default when tar is run by the superuser, but for native recipes the corresponding task is not run as root under pseudo, so pass the flag explicitly. Suggested-by: Richard Purdie (From OE-Core rev: 32f01e57e1e915e8121609fb48b0b0254e625957) Signed-off-by: Jacob Kroon Signed-off-by: Richard Purdie

classes: Only allow network in existing network accessing code

2022-01-12T21:10:24+00:00

Use the newly added network task flag against tasks where network access is expected. This is do_fetch, do_checkuri, do_testimage, do_testsdk and do_testsdkext. We can't disable networking in sstate tasks due to sstate downloads and also so we can report hash equivalence to the server so network access is enabled in sstate tasks. Access within build-appliance do_image is also allowed due to the use of pip, this is a poor example made rather obvious now and needs to be reworked. Network access anywhere else in any other task isn't allowed. (From OE-Core rev: 7ce1e88a3ad85bbb925bb9f7167dc0a5fd1c27f4) Signed-off-by: Richard Purdie

sstate: explicitly name the checkhashes thread pool

2021-11-25T21:55:10+00:00

Give this thread pool a name for clarity. (From OE-Core rev: 57ea50fcfe81f47b93b9302d1aab2e81dcdd3105) Signed-off-by: Ross Burton Signed-off-by: Richard Purdie