DPDK CI discussions
 help / color / mirror / Atom feed
From: Kevin Traynor <ktraynor@redhat.com>
To: Patrick Robb <probb@iol.unh.edu>
Cc: ci@dpdk.org, Lincoln Lavoie <lylavoie@iol.unh.edu>,
	Aaron Conole <aconole@redhat.com>
Subject: Re: 21.11-staging branch run
Date: Wed, 1 Nov 2023 13:52:00 +0000	[thread overview]
Message-ID: <698d637f-8e5e-9ffd-34d7-27b8fa301f02@redhat.com> (raw)
In-Reply-To: <CAJvnSUBF2oondd2rrfCqo+HOmqDCg9e1HfRA+476NDQ=HZOvJg@mail.gmail.com>

Hi Patrick,

On 19/07/2023 16:06, Patrick Robb wrote:
> Hi Kevin,
> 
> I kicked it, so results will be available soon.
> 
> Yesterday, the CI run triggered by you pushing to 21.11-staging had a
> timeout on cloning and checking out the git repo. I'm changing to a shallow
> clone and increasing the timeout in question to alleviate this issue. Sorry
> for the inconvenience.
> 
> Best,
> Patrick
> 
> On Wed, Jul 19, 2023 at 5:15 AM Kevin Traynor <ktraynor@redhat.com> wrote:
> 
>> Hello,
>>
>> I pushed to 21.11-staging branch [0] yesterday, but as of yet the CI did
>> not run on it.
>>
>> Can someone give it a kick ? and re-enable the run on push to branch.
>>
>> thanks,
>> Kevin.
>>
>> [0] https://git.dpdk.org/dpdk-stable/log/?h=21.11-staging
>>
>>
> 

Seems like might be hitting this issue again. I pushed yesterday to 
21.11-staging and it didn't run the CI. I changed and a commit and 
re-pushed as a possible workaround earlier today, but doesn't look like 
it's started anything (at least nothing back yet).

When you have a chance, could you take a look ?

thanks,
Kevin.


  parent reply	other threads:[~2023-11-01 13:52 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-19  9:15 Kevin Traynor
2023-07-19 15:06 ` Patrick Robb
2023-07-19 15:44   ` Kevin Traynor
2023-11-01 13:52   ` Kevin Traynor [this message]
2023-11-02 11:37     ` Kevin Traynor
2023-11-02 13:35       ` Patrick Robb

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=698d637f-8e5e-9ffd-34d7-27b8fa301f02@redhat.com \
    --to=ktraynor@redhat.com \
    --cc=aconole@redhat.com \
    --cc=ci@dpdk.org \
    --cc=lylavoie@iol.unh.edu \
    --cc=probb@iol.unh.edu \
    /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).