From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Alexander Kanavin <alex.kanavin@gmail.com>
Cc: openembedded-core@lists.openembedded.org,
Alexander Kanavin <alex@linutronix.de>
Subject: Re: [OE-core] [PATCH 3/9] bitbake/runqueue: initialize RunQueueExecute before printdiff rather than after
Date: Fri, 15 Dec 2023 16:56:47 +0000 [thread overview]
Message-ID: <e908c28d37f16e3085b45f8c98cd9e68a59edeca.camel@linuxfoundation.org> (raw)
In-Reply-To: <CANNYZj-E4kiuX+R+d29_4Bq3m1hnkgPch709QSKqyHRRAgR1vw@mail.gmail.com>
On Fri, 2023-12-15 at 17:49 +0100, Alexander Kanavin wrote:
> On Fri, 15 Dec 2023 at 17:04, Richard Purdie
> <richard.purdie@linuxfoundation.org> wrote:
>
> > > Meanwhile I'd like to implement what I mentioned in note (1) in patch
> > > 4/9, as it's a real regression that I realized only today as I was
> > > preparing the patchset for submission and now it's bothering me :)
> >
> > Yes, it is and I do agree we need to fix that.
>
> I just completed the fixing. It all works wonderfully in local builds,
> but who knows what situations AB will be able to come up with :) It's
> a bit crowded on the AB right now to start the tests there, so here
> are the patches:
> https://git.yoctoproject.org/poky-contrib/log/?h=akanavin/fix-printdiff
> (I run the tests with a special contrib/kanavin/ branch of
> autobuilder-helper that only runs the three needed selftests, and not
> the whole gigantic set)
Sounds good. I think we are getting to the bottom of some of the
underlying issues which is good and longer term should help usability a
lot.
> I also reverted the gnu-config tweak in that branch as it should be no
> longer necessary.
I was torn on that. I can drop from -next too.
> I'll cherry-pick the bitbake patch before doing any further tests, but
> it's now Friday evening, so anxiously watching ongoing selftests is
> perhaps not the best idea.
Fair enough! I've run that patch through local only testing so far, as
you say, the AB has a lot going on.
I've been torn on waiting for these or building M1 but I'm aiming for
just the CDN fix since this may or may not take a while to settle on
the autobuilder and I don't think we need any more pressure. The
failures are driving Alexandre a bit crazy in swatbot so getting things
sorted is important.
Cheers,
Richard
next prev parent reply other threads:[~2023-12-15 16:56 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-14 13:45 [PATCH 1/9] oeqa/selftest/sstatetests: re-work CDN tests, add local cache tests Alexander Kanavin
2023-12-14 13:45 ` [PATCH 2/9] gnu-config: delete do_compile task Alexander Kanavin
2023-12-14 13:45 ` [PATCH 3/9] bitbake/runqueue: initialize RunQueueExecute before printdiff rather than after Alexander Kanavin
2023-12-14 14:39 ` [OE-core] " Richard Purdie
2023-12-14 17:28 ` Alexander Kanavin
2023-12-15 16:04 ` Richard Purdie
2023-12-15 16:49 ` Alexander Kanavin
2023-12-15 16:56 ` Richard Purdie [this message]
2023-12-14 13:45 ` [PATCH 4/9] bitbake/runqueue: rework 'bitbake -S printdiff' logic Alexander Kanavin
2023-12-14 13:45 ` [PATCH 5/9] selftest/sstatetests: fix up printdiff test to match rework of printdiff logic Alexander Kanavin
2023-12-14 13:45 ` [PATCH 6/9] sstatesig/find_siginfo: unify a disjointed API Alexander Kanavin
2023-12-14 13:45 ` [PATCH 7/9] bitbake-diffsigs/runqueue: adapt to reworked find_siginfo() Alexander Kanavin
2023-12-14 13:45 ` [PATCH 8/9] bitbake/runqueue: prioritize local stamps over sstate signatures in printdiff Alexander Kanavin
2023-12-14 13:45 ` [PATCH 9/9] bitbake/runqueue: add debugging for find_siginfo() calls Alexander Kanavin
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=e908c28d37f16e3085b45f8c98cd9e68a59edeca.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=alex.kanavin@gmail.com \
--cc=alex@linutronix.de \
--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