Hi Kevin,

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.

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.

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.

Patrick Robb

Technical Service Manager

UNH InterOperability Laboratory

21 Madbury Rd, Suite 100, Durham, NH 03824