Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: openembedded-core <openembedded-core@lists.openembedded.org>,
	Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com>
Subject: Re: [OE-core] Latest AB-INT unexplained mystery failure
Date: Tue, 15 Oct 2024 09:18:39 +0100	[thread overview]
Message-ID: <8d74548b102be5f88d1450e3f8734f1b52f1c2f9.camel@linuxfoundation.org> (raw)
In-Reply-To: <17FE0CA1425F2338.24631@lists.openembedded.org>

On Sun, 2024-10-13 at 16:26 +0100, Richard Purdie via
lists.openembedded.org wrote:
> I've spent quite a bit of time trying to reproduce/debug this:
> 
> https://valkyrie.yoctoproject.org//#/builders/35/builds/216/steps/14/logs/stdio
> 
> 2024-10-13 04:12:32,010 - oe-selftest - INFO - RESULTS -
> runtime_test.TestImage.test_testimage_apt: FAILED (218.02s)
> 2024-10-13 04:12:32,010 - oe-selftest - INFO - RESULTS -
> runtime_test.TestImage.test_testimage_dnf: FAILED (155.47s)
> 
> on debian11-vk-1.
> 
> I've a successful test and a failed test testimage output for
> comparison:
> 
> https://valkyrie.yocto.io/pub/shared-failure-data/debian11-vk-1-selftest/log.do_testimage.1487387
> https://valkyrie.yocto.io/pub/shared-failure-data/debian11-vk-1-selftest/log.do_testimage.3323465
> 
> along with qemu serial output:
> 
> https://valkyrie.yocto.io/pub/shared-failure-data/debian11-vk-1-selftest/qemu_boot_log-fail
> https://valkyrie.yocto.io/pub/shared-failure-data/debian11-vk-1-selftest/qemu_boot_log.20241013104106
> 
> I've tried rerunning that exact series of tests on that worker with
> no
> success reproducing the issue. The image was overwritten by a later
> test so we can't retest the exact image. I've checked the journal on
> that system and there isn't anything related around the time this
> happened. The two failures were on different network interfaces and
> both interfaces work on later tests.
> 
> I'm open to ideas...

https://valkyrie.yoctoproject.org//#/builders/35/builds/229/steps/14/logs/stdio

debian11-vk-2 this time. A different runtime test, same kind of network
ing glitch.

Does debian11 have some kind of network management that is interfering?

Cheers,

Richard


  parent reply	other threads:[~2024-10-15  8:18 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 [this message]
     [not found] ` <17FE55BCAF4D83DD.4702@lists.openembedded.org>
2024-10-14 16:11   ` Richard Purdie
2024-10-14 20:40   ` Richard Purdie
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=8d74548b102be5f88d1450e3f8734f1b52f1c2f9.camel@linuxfoundation.org \
    --to=richard.purdie@linuxfoundation.org \
    --cc=mathieu.dubois-briand@bootlin.com \
    --cc=openembedded-core@lists.openembedded.org \
    /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