DPDK CI: 23.11-staging not updated

[David Marchand]

Hello Xueming, Patrick,

On Tue, Jul 9, 2024 at 3:46 AM Patrick Robb <probb at iol.unh.edu> wrote:
>
> +David Marchand +NBU-Contact-Thomas Monjalon (EXTERNAL)
>
> Hi Xueming,
>
> I think the reason why your force push is not resulting in a CI run is
> that our staging branches testing runs from the GitHub mirror, and
> your commit isn't on the mirror, it's only on the dpdk.org git server.
>
> HEAD for dpdk.org:
> https://git.dpdk.org/dpdk-stable/commit/?h=23.11-staging&id=aa0655d5f18f1a185b1b334f4a7e166b85912eda
>
> HEAD for DPDK GitHub mirror:
> https://github.com/DPDK/dpdk-stable/commit/6ee0521feb765d9105241a3f6693762c471655cf
>
> CCing the CI mailing list and some of the maintainers who had
> originally suggested the GitHub mirrors and might understand better
> than me why this is happening.

Patrick,

Thanks for the heads up.
Indeed, I could see that the github mirror was not in sync with
dpdk.org for this branch.


>
> On Mon, Jul 8, 2024 at 8:30 PM Xueming Li <xuemingl at nvidia.com> wrote:
> >
> > Hi Pattrick,
> >
> > Let's try again and see is there new CI triggered:
> >
> > amend my local commit
> >
> > force push to branch:
> >  git push stable 23.11:23.11-staging --force
> > latest commit changed to: aa0655d5f18f1a185b1b334f4a7e166b85912eda
> > dpdk-stable - Data Plane Development Kit - stable branches

Xueming,

Do you have the full output of when you pushed?
I suspect there was some error or warning at the moment you pushed, it
could have been a transient issue (networking issue?).


I resynced the branch by force pushing HEAD^ and HEAD for your -staging branch.
I got no error, and everything looks fine to me.
Can you double check?


-- 
David Marchand