On 10/07/2020 5:02 am, Peter Kjellerstedt wrote:
>Richard Purdie wrote:
Seems like a useful idea. I think the name may need "failed" in the
name to make it clearer what it does. We also need a section for the
classes chapter in the manual.
As another data point, OEQA is using OEQA_DEBUGGING_SAVE
> -Original Message-
> From: openembedded-core@lists.openembedded.org c...@lists.openembedded.org> On Behalf Of Richard Purdie
> Sent: den 8 juli 2020 20:12
> To: Paul Eggleton ; openembedded-
> c...@lists.openembedded.org
> Subject: Re: [OE-core] [RFC PATCH 1/1] clas
On Wed, 2020-07-08 at 11:02 -0700, Paul Eggleton wrote:
> 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
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 en
