netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ihor Solodrai <ihor.solodrai@linux.dev>
To: bpf <bpf@vger.kernel.org>, netdev@vger.kernel.org
Subject: Re: Announcement: BPF CI is down
Date: Mon, 17 Nov 2025 15:46:51 -0800	[thread overview]
Message-ID: <b0df39ab-fdee-4b48-8739-74192cf5a26c@linux.dev> (raw)
In-Reply-To: <938dbf1c-d2b5-42db-8ceb-0121e0cac698@linux.dev>

On 11/17/25 8:26 AM, Ihor Solodrai wrote:
> Hello everyone,
> 
> BPF CI has been down since Friday, November 15, because GitHub appears
> to have disabled the "GitHub Actions" feature for the kernel-patches
> GitHub organization without any prior notice. We do not yet know the
> reason for this.
> 
> Currently, the dashboard [1] shows the following message:
> 
> "GitHub Actions is currently disabled for this repository. Please
> reach out to GitHub Support for assistance."
> 
> This means that no BPF CI jobs, including AI reviews, will run for an
> unknown period of time.
> 
> In the meantime, please be patient with patch reviews, as maintainers
> will need to run the selftests manually.
> 
> [1] https://github.com/kernel-patches/bpf/actions

GitHub support re-enabled access to GitHub actions for kernel-patches
after a manual review of the account.

The workflows are able to launch now.

However please note that BPF CI did not automatically run for patch series
submitted between approximately Nov 15 @ 1am PST and Nov 17 @ 3pm PST.

      reply	other threads:[~2025-11-17 23:47 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-17 16:26 Announcement: BPF CI is down Ihor Solodrai
2025-11-17 23:46 ` Ihor Solodrai [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=b0df39ab-fdee-4b48-8739-74192cf5a26c@linux.dev \
    --to=ihor.solodrai@linux.dev \
    --cc=bpf@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    /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).