From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: openembedded-core <openembedded-core@lists.openembedded.org>,
Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com>
Cc: Ross Burton <ross.burton@arm.com>,
Chuck Wolber <chuck.wolber@boeing.com>,
Adrian Freihofer <adrian.freihofer@siemens.com>,
Marta Rybczynska <marta.rybczynska@syslinbit.com>,
Jon Mason <Jon.Mason@arm.com>,
Michael Halstead <mhalstead@linuxfoundation.org>
Subject: Re: [OE-core] Latest AB-INT unexplained mystery failure
Date: Mon, 14 Oct 2024 21:40:27 +0100 [thread overview]
Message-ID: <98d9bfbfe67799f05a0ad897ec2a91638afde647.camel@linuxfoundation.org> (raw)
In-Reply-To: <17FE55BCAF4D83DD.4702@lists.openembedded.org>
On Mon, 2024-10-14 at 14:46 +0100, Richard Purdie via
lists.openembedded.org wrote:
> e) bitbake server timeout issues
> --------------------------------
>
> https://valkyrie.yoctoproject.org//#/builders/48/builds/185/steps/14/logs/stdio
>
> I've saved
>
> https://valkyrie.yocto.io/pub/shared-failure-data/fedora41-vk-1-selftest/
>
> - the json logs are something we've not had before for that
> - the key message in cookerdaemon is "Idle loop didn't finish queued
> commands after 30s, exiting."
> - that message is there twice, it failed twice
> - can we decode the json logs and get timestamps
> - looks like it happens in particular in the siggen code?
>
> Who/Plan: TBD
>
Happened again:
https://valkyrie.yoctoproject.org/#/builders/48/builds/192
fedora41 again. Logs into:
https://valkyrie.yocto.io/pub/shared-failure-data/fedora41-vk-1-selftest/2
Cheers,
Richard
next prev parent reply other threads:[~2024-10-14 20:40 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <17FE0CA1425F2338.24631@lists.openembedded.org>
2024-10-14 13:46 ` [OE-core] Latest AB-INT unexplained mystery failure Richard Purdie
2024-10-22 13:30 ` Ross Burton
2024-10-15 8:18 ` Richard Purdie
[not found] ` <17FE55BCAF4D83DD.4702@lists.openembedded.org>
2024-10-14 16:11 ` Richard Purdie
2024-10-14 20:40 ` Richard Purdie [this message]
2024-10-15 8:23 ` Richard Purdie
2024-10-15 10:09 ` Richard Purdie
2024-10-19 11:05 ` Richard Purdie
[not found] ` <17FFD5DF016C394D.24795@lists.openembedded.org>
2024-10-19 21:48 ` Richard Purdie
2024-10-21 10:55 ` Alexander Kanavin
2024-10-22 9:58 ` Richard Purdie
2024-10-22 19:48 ` Michael Halstead
2024-10-23 15:28 ` Khem Raj
2024-10-23 15:33 ` Alexander Kanavin
2024-10-23 15:35 ` Richard Purdie
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=98d9bfbfe67799f05a0ad897ec2a91638afde647.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=Jon.Mason@arm.com \
--cc=adrian.freihofer@siemens.com \
--cc=chuck.wolber@boeing.com \
--cc=marta.rybczynska@syslinbit.com \
--cc=mathieu.dubois-briand@bootlin.com \
--cc=mhalstead@linuxfoundation.org \
--cc=openembedded-core@lists.openembedded.org \
--cc=ross.burton@arm.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