From: David Marchand <david.marchand@redhat.com>
To: Xueming Li <xuemingl@nvidia.com>
Cc: Patrick Robb <probb@iol.unh.edu>, Cody Cheng <ccheng@iol.unh.edu>,
"NBU-Contact-Thomas Monjalon (EXTERNAL)" <thomas@monjalon.net>,
ci@dpdk.org
Subject: Re: DPDK CI: 23.11-staging not updated
Date: Tue, 9 Jul 2024 09:37:06 +0200 [thread overview]
Message-ID: <CAJFAV8yzV2=0bNnRX5umbewa29bEgM5p0rkwsct3A=fYNB8bBg@mail.gmail.com> (raw)
In-Reply-To: <CAJvnSUBXSNJ+=ULLsDOh3Ovt6-zRPKEnbays6nEqDrv5kn077Q@mail.gmail.com>
Hello Xueming, Patrick,
On Tue, Jul 9, 2024 at 3:46 AM Patrick Robb <probb@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@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
next prev parent reply other threads:[~2024-07-09 7:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <DM4PR12MB5373EC0E8EAA00300FD5F0DDA1DA2@DM4PR12MB5373.namprd12.prod.outlook.com>
[not found] ` <CAJvnSUBjHnh1TGyezPjHLKVq6zo8T6ci_xS9TRr4YWB1zzbGMg@mail.gmail.com>
[not found] ` <CAMEVEZvx5+Or36QNBLKy36bPO5tDxGtAmzFxhc-Zi1m=Wt-+Nw@mail.gmail.com>
[not found] ` <DM4PR12MB537371ABAC4FC086C0BF5A0BA1DB2@DM4PR12MB5373.namprd12.prod.outlook.com>
2024-07-09 1:46 ` Patrick Robb
2024-07-09 7:37 ` David Marchand [this message]
2024-07-09 13:29 ` Patrick Robb
2024-07-10 8:23 ` Xueming Li
2024-07-10 8:35 ` David Marchand
2024-07-10 11:47 ` Xueming Li
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='CAJFAV8yzV2=0bNnRX5umbewa29bEgM5p0rkwsct3A=fYNB8bBg@mail.gmail.com' \
--to=david.marchand@redhat.com \
--cc=ccheng@iol.unh.edu \
--cc=ci@dpdk.org \
--cc=probb@iol.unh.edu \
--cc=thomas@monjalon.net \
--cc=xuemingl@nvidia.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;
as well as URLs for NNTP newsgroup(s).