DPDK CI discussions
 help / color / mirror / Atom feed
From: Patrick Robb <probb@iol.unh.edu>
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
Subject: Re: DPDK CI: 23.11-staging not updated
Date: Tue, 9 Jul 2024 09:29:23 -0400	[thread overview]
Message-ID: <CAJvnSUCTJmAV+6Sg_JVVGNUwW4HU3HTOeE_8cOZVpQL54oeH_g@mail.gmail.com> (raw)
In-Reply-To: <CAJFAV8yzV2=0bNnRX5umbewa29bEgM5p0rkwsct3A=fYNB8bBg@mail.gmail.com>

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.

  reply	other threads:[~2024-07-09 13:29 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 [this message]
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=CAJvnSUCTJmAV+6Sg_JVVGNUwW4HU3HTOeE_8cOZVpQL54oeH_g@mail.gmail.com \
    --to=probb@iol.unh.edu \
    --cc=ccheng@iol.unh.edu \
    --cc=ci@dpdk.org \
    --cc=david.marchand@redhat.com \
    --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).