DPDK CI discussions
 help / color / mirror / Atom feed
From: Kevin Traynor <ktraynor@redhat.com>
To: ci@dpdk.org
Cc: Patrick Robb <probb@iol.unh.edu>,
	Lincoln Lavoie <lylavoie@iol.unh.edu>,
	Jeremy Spewock <jspewock@iol.unh.edu>,
	Aaron Conole <aconole@redhat.com>,
	David Marchand <david.marchand@redhat.com>
Subject: 21.11-staging CI run
Date: Wed, 5 Apr 2023 13:36:35 +0100	[thread overview]
Message-ID: <c0b20b22-858f-718c-5e12-815736f0e54f@redhat.com> (raw)

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?

thanks,
Kevin.


             reply	other threads:[~2023-04-05 12:36 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-05 12:36 Kevin Traynor [this message]
2023-04-05 14:22 ` Kevin Traynor
2023-04-05 15:26   ` Patrick Robb
2023-04-05 16:13     ` Kevin Traynor

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=c0b20b22-858f-718c-5e12-815736f0e54f@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).