From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: "Alexis Lothoré" <alexis.lothore@bootlin.com>,
"Pokybuild User" <pokybuild@yoctoproject.org>,
yocto@lists.yoctoproject.org
Cc: qa-build-notification@lists.yoctoproject.org
Subject: Re: [yocto] QA notification for completed autobuilder build (yocto-4.3.rc1)
Date: Thu, 19 Oct 2023 13:23:55 +0100 [thread overview]
Message-ID: <40d39fd5eb9136c764f6a81c67701538e94ad028.camel@linuxfoundation.org> (raw)
In-Reply-To: <a97b6ea3-0478-4cb3-a506-ad19ac7a6f86@bootlin.com>
On Thu, 2023-10-19 at 10:36 +0200, Alexis Lothoré wrote:
> Hello,
>
> On 10/18/23 08:16, Pokybuild User wrote:
> >
> > A build flagged for QA (yocto-4.3.rc1) was completed on the autobuilder and is available at:
> >
> >
> > https://autobuilder.yocto.io/pub/releases/yocto-4.3.rc1
>
> The regression report looks worryingly empty. It has been generated with
> yocto-4.2 as comparison base. When taking a look at yocto-testresults content
> for it, I only find a few test results (11, while it should be something around
> 300). I am not sure yet if we did some mistakes while re-uploading manually
> missing tests results during the 4.2 cycle, or if tests results are indeed
> suffering some issues for release builds (this is repeatable on different 4.2.x
> releases).
I'd noticed that too, not sure what happened but it wasn't what I'd
expected. It would be good to understand what went wrong.
> So in the mean time, here is a manual regression report between 4.3_M3 and
> yocto-4.3.rc1:
>
> https://pastebin.com/6QbfGstR
>
> The report has a "rate limit" applied for noisy regression (patch incoming)
I was thinking about ideas like printing the regressions first, then
the matches. I think Ross has some good feedback about how we can
improve things.
Cheers,
Richard
next prev parent reply other threads:[~2023-10-19 12:24 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-18 6:16 QA notification for completed autobuilder build (yocto-4.3.rc1) Pokybuild User
2023-10-18 6:29 ` [qa-build-notification] " Richard Purdie
2023-10-18 15:32 ` [tsc] " Ross Burton
2023-10-18 19:43 ` Richard Purdie
2023-10-19 8:36 ` [yocto] " Alexis Lothoré
2023-10-19 11:04 ` Ross Burton
2023-10-19 12:28 ` Alexis Lothoré
2023-10-19 12:55 ` Richard Purdie
2023-10-19 12:23 ` Richard Purdie [this message]
2023-10-19 14:06 ` [qa-build-notification] " Tham, Jing Hui
2023-10-19 16:03 ` 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=40d39fd5eb9136c764f6a81c67701538e94ad028.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=alexis.lothore@bootlin.com \
--cc=pokybuild@yoctoproject.org \
--cc=qa-build-notification@lists.yoctoproject.org \
--cc=yocto@lists.yoctoproject.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