public inbox for openembedded-core@lists.openembedded.org
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: paul.eggleton@linux.microsoft.com,
	 openembedded-core@lists.openembedded.org
Subject: Re: [OE-core] [PATCH 1/1] classes: add new retain class for retaining build results
Date: Tue, 30 Jul 2024 09:13:05 +0100	[thread overview]
Message-ID: <57e05ea2308501897f3dab545047e32187d7713f.camel@linuxfoundation.org> (raw)
In-Reply-To: <91375a039483ece87de8835f50cf4b4b0ed474ca.1722211934.git.paul.eggleton@linux.microsoft.com>

Hi Paul,

On Sun, 2024-07-28 at 17:22 -0700, Paul Eggleton via
lists.openembedded.org wrote:
> From: Paul Eggleton <paul.eggleton@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.eggleton@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



      reply	other threads:[~2024-07-30  8:13 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-29  0:22 [PATCH 0/1] classes: add new retain class for retaining build results Paul Eggleton
2024-07-29  0:22 ` [PATCH 1/1] " Paul Eggleton
2024-07-30  8:13   ` Richard Purdie [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=57e05ea2308501897f3dab545047e32187d7713f.camel@linuxfoundation.org \
    --to=richard.purdie@linuxfoundation.org \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=paul.eggleton@linux.microsoft.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox