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.