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>,
	Joshua Watt <JPEWhacker@gmail.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: Tue, 15 Oct 2024 11:09:51 +0100	[thread overview]
Message-ID: <2bad4dab835a0ce9710e576a2171fb9f70a78457.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:
> 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.
> 
> a) insane do_package_qa intermittent failures
> ---------------------------------------------
> 
> Two levels of probems. The cachedpath code returns False instead of
> exceptions so there was unexpected API changes. The recent insane
> changes also stopped handling DEBIAN files correctly leading to
> races.
> This is perhaps the best backtrace we have:
> 
> https://valkyrie.yoctoproject.org//#/builders/43/builds/246
> 
> Who/Plan: RP has a partial revert for the first part to fix builds.
> Ross is aware and working on the second.

I tested Ross' patch for this and unfortunate it caused a new problem
to appear.

I accidentally triggered two a-full builds at once, there was also a
scarthgap build running at the time.

The patch from Ross caused all the do_package_qa tasks to rerun at once
in parallel which caused writes to the hash equivalence server. This
caused widespread timeout errors and took out all the builds including
the scarthgap one in parallel.

https://valkyrie.yoctoproject.org/#/builders/4/builds/257
https://valkyrie.yoctoproject.org/#/builders/2/builds/253
https://valkyrie.yoctoproject.org/#/builders/89/builds/236/steps/16/logs/stdio
https://valkyrie.yoctoproject.org/#/builders/40/builds/242/steps/11/logs/stdio

and many more.

Joshua: Is there a performance issue with many writes in parallel to
hashequiv?

The stats info off the server was:

    "requests": {
        "average": 0.042532518429623176,
        "max_time": 3.0534732329833787,
        "num": 73325629,
        "stdev": 0.06959859907598737,
        "total_time": 3118723.6668062117
    }

Cheers,

Richard



  parent reply	other threads:[~2024-10-15 10:10 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
2024-10-15  8:23   ` Richard Purdie
2024-10-15 10:09   ` Richard Purdie [this message]
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=2bad4dab835a0ce9710e576a2171fb9f70a78457.camel@linuxfoundation.org \
    --to=richard.purdie@linuxfoundation.org \
    --cc=JPEWhacker@gmail.com \
    --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