On Tue, Dec 20, 2022 at 11:49 AM Richard Purdie
<[email protected]> wrote:
>
> On Tue, 2022-12-20 at 13:50 -0500, Bruce Ashfield wrote:
> > On Tue, Dec 20, 2022 at 1:48 PM Steve Sakoman <[email protected]> wrote:
> > >
> > > On Tue, Dec 20, 2022 at 4:46 AM Bruce Ashfield <[email protected]> 
> > > wrote:
> > > >
> > > > On Tue, Dec 20, 2022 at 9:27 AM Steve Sakoman <[email protected]> wrote:
> > > > >
> > > > > On Mon, Dec 19, 2022 at 7:41 AM <[email protected]> wrote:
> > > > > >
> > > > > > From: Bruce Ashfield <[email protected]>
> > > > > >
> > > > > > Updating  to the latest korg -stable release that comprises
> > > > > > the following commits:
> > > > > >
> > > > > > [...]
> > > > > > -SRCREV_machine_qemuarm ?= 
> > > > > > "13d88d2fc15f1edfa91378bc3a76aa4274969ed8"
> > > > > > -SRCREV_machine_qemuarm64 ?= 
> > > > > > "14d0e6d0baf0c7b2308ff1270bd706f927c72df4"
> > > > > > -SRCREV_machine_qemumips ?= 
> > > > > > "11472a4308590f1858d1ba7bb03bdc25cd2c9b3f"
> > > > > > -SRCREV_machine_qemuppc ?= 
> > > > > > "daf1282f1c6fd653fcae25e8d1d49540a932baeb"
> > > > > > -SRCREV_machine_qemuriscv64 ?= 
> > > > > > "15231fe2f4542b044e279e53269ee506bced9988"
> > > > > > -SRCREV_machine_qemux86 ?= 
> > > > > > "15231fe2f4542b044e279e53269ee506bced9988"
> > > > > > -SRCREV_machine_qemux86-64 ?= 
> > > > > > "15231fe2f4542b044e279e53269ee506bced9988"
> > > > > > -SRCREV_machine_qemumips64 ?= 
> > > > > > "31f08b9f81298e80e00ea37886db6f88092a5cf6"
> > > > > > -SRCREV_machine ?= "15231fe2f4542b044e279e53269ee506bced9988"
> > > > > > -SRCREV_meta ?= "3e7ca0fe77707fabb1beefd5d3cd322a4db1eb41"
> > > > > > +SRCREV_machine_qemuarm ?= 
> > > > > > "32654a547b05ba63c604503fc865d7052ae96992"
> > > > > > +SRCREV_machine_qemuarm64 ?= 
> > > > > > "2bd8ca7c0973870753b103107513689a598383d7"
> > > > > > +SRCREV_machine_qemumips ?= 
> > > > > > "84a8ba0ada556ba3307c33e2b5a0ca8f9e3df1dd"
> > > > > > +SRCREV_machine_qemuppc ?= 
> > > > > > "20db90d7935c8760bfc68c0de4f7d7085cba7c14"
> > > > > > +SRCREV_machine_qemuriscv64 ?= 
> > > > > > "921d9e22542506ba26c2e5e2f25ec00ff9bffa63"
> > > > > > +SRCREV_machine_qemux86 ?= 
> > > > > > "921d9e22542506ba26c2e5e2f25ec00ff9bffa63"
> > > > > > +SRCREV_machine_qemux86-64 ?= 
> > > > > > "921d9e22542506ba26c2e5e2f25ec00ff9bffa63"
> > > > >
> > > > > I suspect you forgot to push this final change set to the linux-yocto 
> > > > > repo!
> > > >
> > > > Hmm. nope. Everything is pushed, disregard the updates, I'll have
> > > > another look at it the second week of January.
> > >
> > > It wasn't there earlier this morning when I sent the email, but now it
> > > has magically appeared!
> > >
> > > So nothing for you to do at this point.  I've restarted the build and
> > > will let you know if I run into any other issues.
> >
> > odd. I was pushing some 6.1 changes, but git didn't report anything coming
> > from the 5.4 branches.
> >
> > Fingers crossed that my script updates to the SRCREVs and what is there
> > now are a match!
>
> FWIW it takes time for the revisions to mirror from the push server to
> the other public git servers. For the kernel it probably takes longer.

Yes, I'm familiar with the delay.  In this case though the patch
emails arrived yesterday at 7:41am and I did the build hours later in
the early afternoon. I'm not sure when Bruce did the push, I assume it
was before he sent the patches!

I noticed the failures in the early evening and stopped the build.  I
didn't look at the errors till this morning and noticed when I browsed
the linux-yocto repo that the requested commit id wasn't present. IIRC
the top of tree was the 5.4.227 tag.  It was at that point that I sent
the email.

Later in the morning I checked linux-yocto again and the referenced
commit was now top of tree and my build succeeded.

Not sure if any of this is helpful in debugging mirror tarball
breakage, but thought I would record the details while they were still
fresh in my mind.

Steve


> I think these builds with "missing" revisions and the older fetcher in
> dunfell caused some kernel mirror tarballs to get deleted and broke the
> esdk kernel module tests in my build. That shouldn't happen but somehow
> seemed to :/.
>
> Cheers,
>
> Richard
>
> 
>
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#174886): 
https://lists.openembedded.org/g/openembedded-core/message/174886
Mute This Topic: https://lists.openembedded.org/mt/95769673/21656
Group Owner: [email protected]
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[[email protected]]
-=-=-=-=-=-=-=-=-=-=-=-

Reply via email to