From: Patrick Robb <probb@iol.unh.edu>
To: Kevin Traynor <ktraynor@redhat.com>
Cc: ci@dpdk.org, Lincoln Lavoie <lylavoie@iol.unh.edu>,
Aaron Conole <aconole@redhat.com>
Subject: Re: 21.11-staging branch run
Date: Wed, 19 Jul 2023 11:06:56 -0400 [thread overview]
Message-ID: <CAJvnSUBF2oondd2rrfCqo+HOmqDCg9e1HfRA+476NDQ=HZOvJg@mail.gmail.com> (raw)
In-Reply-To: <b807c9ca-e58f-fa47-0d68-4470ef9a120f@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 842 bytes --]
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
>
>
--
Patrick Robb
Technical Service Manager
UNH InterOperability Laboratory
21 Madbury Rd, Suite 100, Durham, NH 03824
www.iol.unh.edu
[-- Attachment #2: Type: text/html, Size: 3228 bytes --]
next prev parent reply other threads:[~2023-07-19 15:07 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 [this message]
2023-07-19 15:44 ` Kevin Traynor
2023-11-01 13:52 ` Kevin Traynor
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='CAJvnSUBF2oondd2rrfCqo+HOmqDCg9e1HfRA+476NDQ=HZOvJg@mail.gmail.com' \
--to=probb@iol.unh.edu \
--cc=aconole@redhat.com \
--cc=ci@dpdk.org \
--cc=ktraynor@redhat.com \
--cc=lylavoie@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).