Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Ross Burton <Ross.Burton@arm.com>
To: openembedded-core <openembedded-core@lists.openembedded.org>
Subject: Re: [OE-core] Latest AB-INT unexplained mystery failure
Date: Tue, 22 Oct 2024 13:30:39 +0000	[thread overview]
Message-ID: <DBDDCAAE-5B12-4217-AD0D-F78B667DF56E@arm.com> (raw)
In-Reply-To: <43a7cfaa3cc1304ba4c5c43a802d97d7edb06233.camel@linuxfoundation.org>

On 14 Oct 2024, at 14:46, Richard Purdie <richard.purdie@linuxfoundation.org> wrote:
> It was suggested I should write down a list of other issues we have on
> the autobuilder right now. Some of these are related to the transition
> to new infrastructure, some are previously seen issues occurring more
> frequently, some are entirely new. I appreciate these should all have
> bugs. I'm copying various people including those helping with SWAT so
> we can transition those we don't get solved into bugzilla.

I thought I’d send an update to this mail:

> a) insane do_package_qa intermittent failures
> ——————————————————————

This has now been fixed.

> b) docs build failing in missing inkscape
> -----------------------------------------

This was the AB building more than we expected, and is now resolved.

> c) source mirroring failing on AB
> ————————————————

This is still in progress.

> d) CDN artefacts are failing

This is still in progress.

> e) bitbake server timeout issues
> --------------------------------

Still TDB.

> f) CVE database corruption
> --------------------------

Prognosis is good, appears to be fixed in master.

> g) Toaster test issues
> ----------------------

RP has discovered his inner web developer and is making good progress on these.

> i) rust toolchain test failures mips/ppc

These are proving tricky to reproduce on demand.  As the platforms are not supported upstream I think we should skip the rust tests entirely.

> j) SPDX build warnings

Appears to be resolved with Josh’s patch.

> k) ssh test still causing failures

Fixed.

Cheers,
Ross

  reply	other threads:[~2024-10-22 13:31 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 [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-15  8:18 ` 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=DBDDCAAE-5B12-4217-AD0D-F78B667DF56E@arm.com \
    --to=ross.burton@arm.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