From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: "Yann E. MORIN" <yann.morin.1998@free.fr>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [autobuild.buildroot.net] Daily results for 2021-11-03
Date: Fri, 5 Nov 2021 09:25:02 +0100 [thread overview]
Message-ID: <20211105092502.5e3ac821@windsurf> (raw)
In-Reply-To: <20211104214829.GC2400@scaer>
On Thu, 4 Nov 2021 22:48:29 +0100
"Yann E. MORIN" <yann.morin.1998@free.fr> wrote:
> Hint, and to serve as my own memory: if investigating a reported-unknown
> failure, just grab the build-time.log.gz, decompress it, and pass it
> through this python3 script:
>
>
> with open('build-time.log', 'r') as f:
> lines = [l.rstrip('\n\r') for l in f.readlines()]
> pkg = dict()
> for l in lines:
> items = [i.strip() for i in l.split(':')]
> if items[1] == 'start':
> pkg[items[3]] = items[2]
> else:
> del pkg[items[3]]
> print(pkg)
>
> This reports all the packages (usually one) that had a step started that
> did not end, e.g.;
>
> {'tpm2-tss': 'configure'}
Should we augment the logic that detects the failure reason with
something like this, when the reason is "unknown" ? It would be ideal
to also get the package version, so we could get the exact same
information as we have with "normal" failures.
Thomas
--
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2021-11-05 8:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-04 6:54 [Buildroot] [autobuild.buildroot.net] Daily results for 2021-11-03 Thomas Petazzoni
2021-11-04 21:48 ` Yann E. MORIN
2021-11-05 8:25 ` Thomas Petazzoni [this message]
2021-11-05 21:23 ` Yann E. MORIN
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=20211105092502.5e3ac821@windsurf \
--to=thomas.petazzoni@bootlin.com \
--cc=buildroot@buildroot.org \
--cc=yann.morin.1998@free.fr \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.