Re: DPDK CI: 23.11-staging not updated

Re: DPDK CI: 23.11-staging not updated

[Patrick Robb]

+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.

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

Re: DPDK CI: 23.11-staging not updated

[David Marchand]

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

Re: DPDK CI: 23.11-staging not updated

[Patrick Robb]

On Tue, Jul 9, 2024 at 3:37 AM David Marchand <david.marchand@redhat.com> wrote:
> 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?).
>
>

From the part of the conversation ahead of adding you to CC list, it
looks like Xueming tried force pushing twice yesterday, and CI was not
triggered either time. So, this reduces the likelihood of a transient
error.

But I will let Xueming tell their side.

Re: DPDK CI: 23.11-staging not updated

[Xueming Li]

[-- Attachment #1: Type: text/plain, Size: 1676 bytes --]

Hi all,

I did see some error during pushing, but the remote branch updated correctly, so I ignored the message. Here is the complete log:

git push stable 23.11:23.11-staging --force
Enumerating objects: 5, done.
Counting objects: 100% (5/5), done.
Delta compression using up to 8 threads
Compressing objects: 100% (2/2), done.
Writing objects: 100% (3/3), 300 bytes | 300.00 KiB/s, done.
Total 3 (delta 1), reused 0 (delta 0), pack-reused 0
remote: Host key verification failed.
remote: fatal: Could not read from remote repository.
remote:
remote: Please make sure you have the correct access rights
remote: and the repository exists.
To dpdk.org:dpdk-stable.git
 + fca030545a...aa0655d5f1 23.11 -> 23.11-staging (forced update)

________________________________
From: Patrick Robb <probb@iol.unh.edu>
Sent: Tuesday, July 9, 2024 9:29 PM
To: David Marchand <david.marchand@redhat.com>
Cc: Xueming Li <xuemingl@nvidia.com>; Cody Cheng <ccheng@iol.unh.edu>; NBU-Contact-Thomas Monjalon (EXTERNAL) <thomas@monjalon.net>; ci@dpdk.org <ci@dpdk.org>
Subject: Re: DPDK CI: 23.11-staging not updated

On Tue, Jul 9, 2024 at 3:37 AM David Marchand <david.marchand@redhat.com> wrote:
> 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?).
>
>

From the part of the conversation ahead of adding you to CC list, it
looks like Xueming tried force pushing twice yesterday, and CI was not
triggered either time. So, this reduces the likelihood of a transient
error.

But I will let Xueming tell their side.

[-- Attachment #2: Type: text/html, Size: 5334 bytes --]

Re: DPDK CI: 23.11-staging not updated

[David Marchand]

Hello,

On Wed, Jul 10, 2024 at 10:23 AM Xueming Li <xuemingl@nvidia.com> wrote:
>
> I did see some error during pushing, but the remote branch updated correctly, so I ignored the message. Here is the complete log:

Ignoring errors is rarely a good thing.

>
> git push stable 23.11:23.11-staging --force
> Enumerating objects: 5, done.
> Counting objects: 100% (5/5), done.
> Delta compression using up to 8 threads
> Compressing objects: 100% (2/2), done.
> Writing objects: 100% (3/3), 300 bytes | 300.00 KiB/s, done.
> Total 3 (delta 1), reused 0 (delta 0), pack-reused 0
> remote: Host key verification failed.
> remote: fatal: Could not read from remote repository.
> remote:
> remote: Please make sure you have the correct access rights
> remote: and the repository exists.

This is the part that pushes to the github mirror.

I updated dpdk.org host keys for github.
Can you retry please?


> To dpdk.org:dpdk-stable.git
>  + fca030545a...aa0655d5f1 23.11 -> 23.11-staging (forced update)


-- 
David Marchand

Re: DPDK CI: 23.11-staging not updated

[Xueming Li]

[-- Attachment #1: Type: text/plain, Size: 2131 bytes --]

Hi David,

Still the same issue:

git push stable 23.11:23.11-staging --force

Enumerating objects: 5, done.
Counting objects: 100% (5/5), done.
Delta compression using up to 8 threads
Compressing objects: 100% (2/2), done.
Writing objects: 100% (3/3), 300 bytes | 300.00 KiB/s, done.
Total 3 (delta 1), reused 0 (delta 0), pack-reused 0
remote: Host key verification failed.
remote: fatal: Could not read from remote repository.
remote:
remote: Please make sure you have the correct access rights
remote: and the repository exists.
To dpdk.org:dpdk-stable.git
 + aa0655d5f1...d51d731102 23.11 -> 23.11-staging (forced update)


Feel free to amend the last patch and force push.

________________________________
From: David Marchand <david.marchand@redhat.com>
Sent: Wednesday, July 10, 2024 4:35 PM
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 <ci@dpdk.org>
Subject: Re: DPDK CI: 23.11-staging not updated

Hello,

On Wed, Jul 10, 2024 at 10:23 AM Xueming Li <xuemingl@nvidia.com> wrote:
>
> I did see some error during pushing, but the remote branch updated correctly, so I ignored the message. Here is the complete log:

Ignoring errors is rarely a good thing.

>
> git push stable 23.11:23.11-staging --force
> Enumerating objects: 5, done.
> Counting objects: 100% (5/5), done.
> Delta compression using up to 8 threads
> Compressing objects: 100% (2/2), done.
> Writing objects: 100% (3/3), 300 bytes | 300.00 KiB/s, done.
> Total 3 (delta 1), reused 0 (delta 0), pack-reused 0
> remote: Host key verification failed.
> remote: fatal: Could not read from remote repository.
> remote:
> remote: Please make sure you have the correct access rights
> remote: and the repository exists.

This is the part that pushes to the github mirror.

I updated dpdk.org host keys for github.
Can you retry please?


> To dpdk.org:dpdk-stable.git
>  + fca030545a...aa0655d5f1 23.11 -> 23.11-staging (forced update)


--
David Marchand


[-- Attachment #2: Type: text/html, Size: 6803 bytes --]