From: Xueming Li <xuemingl@nvidia.com>
To: Patrick Robb <probb@iol.unh.edu>,
David Marchand <david.marchand@redhat.com>
Cc: 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
Date: Wed, 10 Jul 2024 08:23:43 +0000 [thread overview]
Message-ID: <BN9PR12MB5366AB354A2EA8C20560369DA1A42@BN9PR12MB5366.namprd12.prod.outlook.com> (raw)
In-Reply-To: <CAJvnSUCTJmAV+6Sg_JVVGNUwW4HU3HTOeE_8cOZVpQL54oeH_g@mail.gmail.com>
[-- 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 --]
next prev parent reply other threads:[~2024-07-10 8:23 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
2024-07-09 13:29 ` Patrick Robb
2024-07-10 8:23 ` Xueming Li [this message]
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=BN9PR12MB5366AB354A2EA8C20560369DA1A42@BN9PR12MB5366.namprd12.prod.outlook.com \
--to=xuemingl@nvidia.com \
--cc=ccheng@iol.unh.edu \
--cc=ci@dpdk.org \
--cc=david.marchand@redhat.com \
--cc=probb@iol.unh.edu \
--cc=thomas@monjalon.net \
/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).