From: Kevin Traynor <ktraynor@redhat.com>
To: Patrick Robb <probb@iol.unh.edu>
Cc: ci@dpdk.org, Lincoln Lavoie <lylavoie@iol.unh.edu>,
Jeremy Spewock <jspewock@iol.unh.edu>,
Aaron Conole <aconole@redhat.com>,
David Marchand <david.marchand@redhat.com>
Subject: Re: 21.11-staging CI run
Date: Wed, 5 Apr 2023 17:13:18 +0100 [thread overview]
Message-ID: <3001ba65-d089-4f1b-5f05-56f76e9150db@redhat.com> (raw)
In-Reply-To: <CAJvnSUC_ETcFvN+RwSVJ6Tz2Ez=jYFrpa2cJ+z3GMop=hB-JRw@mail.gmail.com>
On 05/04/2023 16:26, Patrick Robb wrote:
> Hi Kevin,
>
Hi Patrick,
> We do use the Github mirror for the stable branches. However, the Github
> key change is not relevant here because we use https for our git operations
> on the stable branches.
>
> This morning when you pushed to 21.11-staging, our system timed out when
> checking out to your commit. Just to check that the issue was reproducible,
> I reran the pipeline, and this time the checkout completed fine and a full
> series of tests was kicked off for 21.11-staging. I'm not sure if git was
> in a bad state or what, but I'm trying to find out more.
>
ok, cool. It might be just a once off, I haven't seen that in the past.
As a workaround, I can force push as it's a staging branch to re-trigger
if it occurs again.
> Also, the scatter test failure you see on the 21.11-staging results is an
> infra issue on our side which is now resolved, and a rerun for that scatter
> test is put in so that will be corrected soon.
>
Thanks for letting me know. I noticed that and saw that I hadn't pushed
new Bcm patches, so figured it was an test/infra issue.
thanks,
Kevin.
> On Wed, Apr 5, 2023 at 10:23 AM Kevin Traynor <ktraynor@redhat.com> wrote:
>
>> On 05/04/2023 13:36, Kevin Traynor wrote:
>>> Hi,
>>>
>>> I noticed that 21.11-staging was not kicking off CI the last 2-3 times I
>>> pushed to it.
>>>
>>> It may have been caused by the recent github key change?
>>>
>>> That is resolved now for dpdk.org -> github replication and I pushed
>>> today, but I still didn't see any CI run started.
>>>
>>> I'm not sure if 21.11-staging is monitoring dpdk.org or github, and also
>>> has an issue with keys, or if there is some other issue.
>>>
>>> Could someone take a look and check?
>>>
>>
>> Update, I see some tests running on 21.11-staging now. Not sure if it
>> was just a delay after my push earlier, or someone updated something -
>> if so, thanks!
>>
>>> thanks,
>>> Kevin.
>>
>>
>
prev parent reply other threads:[~2023-04-05 16:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-05 12:36 Kevin Traynor
2023-04-05 14:22 ` Kevin Traynor
2023-04-05 15:26 ` Patrick Robb
2023-04-05 16:13 ` Kevin Traynor [this message]
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=3001ba65-d089-4f1b-5f05-56f76e9150db@redhat.com \
--to=ktraynor@redhat.com \
--cc=aconole@redhat.com \
--cc=ci@dpdk.org \
--cc=david.marchand@redhat.com \
--cc=jspewock@iol.unh.edu \
--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).