linux/poky.git/meta/classes/sstate.bbclass, branch master-next2

Remove SSTATE_HASHEQUIV_SERVER

2019-09-18T10:52:02+00:00

Removes all references to the SSTATE_HASHEQUIV_SERVER variable. This variable is redundant now that BB_HASHSERVE is present. (From OE-Core rev: fb74079c0a66a88aaa789d9a35bd5d188c369110) Signed-off-by: Joshua Watt Signed-off-by: Richard Purdie

sstate/sstatesig: Update to new form of BB_HASHCHECK_FUNCTION

2019-08-06T10:24:26+00:00

Bitbake has updated to a cleaned up form of BB_HASHCHECK_FUNCTION, adapt to this cleanup. This is an API breaking change. (From OE-Core rev: a4d413d8d809132b0e0a5dd673a36e2bd0e0be4c) Signed-off-by: Richard Purdie

sstate: Reduce race windows

2019-08-03T22:56:01+00:00

When we write to the sstate directory we try to do so atomically so consumers either see one version or another but never an imcomplete file. Unfortunately this is reliant on filesystem support and with some NFS configurations a replaced file would be lost from memory even if users held open descriptors. It makes sense to try and avoid replacing existing files where we can. (From OE-Core rev: 18cdc087fd5da30e2b31f3d4e81b153cd36ca844) Signed-off-by: Richard Purdie

classes/sstate: regenerate sstate when signing enabled

2019-07-31T22:03:01+00:00

This change ensures that the task signatures changes, and therefore sstate tasks are rerun, when signing is enabled. This has the positive outcome that if signing is enabled new signed shared state objects will be produced, rather than just signing shared state objects for tasks where no work has been performed yet. The downside of this change is that enabling/disabling sstate object signing alters the taskhash and results in rebuilding the world. (From OE-Core rev: ef60c65e3856682b90b17ae06a1b675756fd4496) Signed-off-by: Joshua Lock Signed-off-by: Richard Purdie

classes/sstate: don't use unsigned sstate when verification enabled

2019-07-27T21:45:30+00:00

When signature verification of shared state objects is enabled (SSTATE_VERIFY_SIG) use of an unsigned object, even though it produces a warning, seems unexpected. Instead skip unsigned objects and force the non-accelerated task to be run. (From OE-Core rev: 571235978d98552e3734bf382454dd51272db782) Signed-off-by: Joshua Lock Signed-off-by: Richard Purdie

sstate: fix log message

2019-07-27T21:45:30+00:00

Referring to the sstate object as a staging package is an artefact of the code's origins. Switch to referring to an "Sstate package" in order to be more accurate and consistent with the rest of the file. (From OE-Core rev: 06559c1ed86dbce53505f9ed98111fe9d0b97ed7) Signed-off-by: Joshua Lock Signed-off-by: Richard Purdie

sstate: Add tweak to avoid multiple sstate stats messages

2019-07-15T08:29:59+00:00

After the recent changes in bitbake to runqueue, we need to recheck sstate validity, particularly in multiconfig builds where tasks have the same checksum. Avoid printing summary messages in this case. Also avoid multiple events to toaster which may not be expecting that at later points in the code. (From OE-Core rev: 227125b96ad6fb0cf6e259e787d83415993db847) Signed-off-by: Richard Purdie

sstate.bbclass: Use bb.utils.to_boolean() for BB_NO_NETWORK

2019-04-10T12:46:17+00:00

Make it consistent with bitbake (From OE-Core rev: 7fb540c3199bc2b82d60fff678b5e588ab4d1ad6) Signed-off-by: Robert Yang Signed-off-by: Richard Purdie

sstate.bbclass: make sure changes to SSTATE_SCAN_FILES are not ignored

2019-01-24T17:45:25+00:00

When changing the SSTATE_SCAN_FILES variable in a recipe it doesn't cause a rebuild, so if there's a sstate-cache available with "bad" sstate data in it that will still be used even though the recipe is updated to address this. [YOCTO #13144] (From OE-Core rev: ea3526961920a229e0bb5fb459952be89fce2255) Signed-off-by: Alexander Kanavin Signed-off-by: Richard Purdie

classes/sstate: Update output hash

2019-01-22T14:35:58+00:00

Updates the output hash calculation for determining if tasks are equivalent. The new algorithm does the following based on feedback: 1) The output hash function was moved to the OE library. 2) All files are printed in a single line tabular format 3) Prints the file type and mode in a user-friendly ls-like format 4) Includes the file owner and group (by name, not ID). These are only included if the task is run under pseudo since that is the only time they can be consistently determined. 5) File size is included for regular files (From OE-Core rev: 4bd297dfe92851f3b44f6b5560bac9d8f9ccf9f2) Signed-off-by: Joshua Watt Signed-off-by: Richard Purdie