Hi Paul,
On Sun, 2024-07-28 at 17:22 -0700, Paul Eggleton via
lists.openembedded.org wrote:
> From: Paul Eggleton <paul.eggle...@microsoft.com>
>
> If you are running your builds inside an environment where you don't
> have access to the build tree (e.g. an autobuilder where you can only
> download final artifacts such as images), then debugging build
> failures
> can be difficult - you can't examine log files, the source tree or
> output files. When enabled, by default this class will retain the
> work
> directory for any recipe that has a task failure in the form of a
> tarball, and can also be configured to save other directories on
> failure
> or always.
>
> It puts these tarballs in a configurable location (${TMPDIR}/retained
> by
> default), where they can be picked up by a separate process and made
> available as downloadable artifacts.
>
> Signed-off-by: Paul Eggleton <paul.eggle...@microsoft.com>
Thanks for the patch, looks like it could be useful for some contexts.
I ran it through the autobuilder and whilst one selftest passed there
were failures too:
https://autobuilder.yoctoproject.org/typhoon/#/builders/80/builds/6961/steps/14/logs/stdio
https://autobuilder.yoctoproject.org/typhoon/#/builders/127/builds/3662/steps/15/logs/stdio
https://autobuilder.yoctoproject.org/typhoon/#/builders/87/builds/7016/steps/14/logs/stdio
https://autobuilder.yoctoproject.org/typhoon/#/builders/86/builds/7026/steps/14/logs/stdio
Maybe everything after the first run failed so a build from sstate
issue at a total guess?
Cheers,
Richard
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#202667):
https://lists.openembedded.org/g/openembedded-core/message/202667
Mute This Topic: https://lists.openembedded.org/mt/107600988/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
