ci: temporarily disable focal job in merge-queue and nightly flows#954
ci: temporarily disable focal job in merge-queue and nightly flows#954
Conversation
Launchpad's PPA infrastructure (ppa.launchpad.net / ppa.launchpadcontent.net) has been intermittently refusing connections for several days, breaking focal's install of gcc-11 from ppa:ubuntu-toolchain-r/test which is required because focal needs gcc-11 for the SVS code path's C++20 features. Comment out the focal job in both event-merge-to-queue.yml and event-nightly.yml (and the corresponding entries in their respective needs: lists) so the merge queue and nightly notifier are not blocked by this upstream outage. focal.yml itself is untouched and remains manually-triggerable via workflow_dispatch. To be reverted once a durable solution (likely a pre-built CI image with gcc-11 baked in, removing the per-run Launchpad dependency) is in place.
🛡️ Jit Security Scan Results✅ No security findings were detected in this PR
Security scan by Jit
|
There was a problem hiding this comment.
Pull request overview
This PR temporarily removes the Ubuntu 20.04 (“focal”) CI job from the merge-queue and nightly workflows so those automated flows aren’t blocked by upstream Launchpad PPA connectivity failures, while keeping focal.yml available for manual runs.
Changes:
- Commented out the
focaljob in the merge-queue workflow. - Commented out the
focaljob in the nightly workflow. - Removed
focalfrom the correspondingneeds:lists so validation/notification jobs no longer wait on it.
Reviewed changes
Copilot reviewed 2 out of 2 changed files in this pull request and generated 3 comments.
| File | Description |
|---|---|
| .github/workflows/event-nightly.yml | Disables focal in nightly and removes it from notify-on-failure.needs. |
| .github/workflows/event-merge-to-queue.yml | Disables focal in merge-queue and removes it from pr-validation.needs. |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
|
Backport failed for Please cherry-pick the changes locally and resolve any conflicts. git fetch origin 0.6
git worktree add -d .worktree/backport-954-to-0.6 origin/0.6
cd .worktree/backport-954-to-0.6
git switch --create backport-954-to-0.6
git cherry-pick -x fe175897c1dff9e9f5adb41b030baa34993bcce9 |
|
Backport failed for Please cherry-pick the changes locally and resolve any conflicts. git fetch origin 0.7
git worktree add -d .worktree/backport-954-to-0.7 origin/0.7
cd .worktree/backport-954-to-0.7
git switch --create backport-954-to-0.7
git cherry-pick -x fe175897c1dff9e9f5adb41b030baa34993bcce9 |
|
Backport failed for Please cherry-pick the changes locally and resolve any conflicts. git fetch origin 0.8
git worktree add -d .worktree/backport-954-to-0.8 origin/0.8
cd .worktree/backport-954-to-0.8
git switch --create backport-954-to-0.8
git cherry-pick -x fe175897c1dff9e9f5adb41b030baa34993bcce9 |
|
Git push to origin failed for 8.2 with exitcode 1 |
|
Git push to origin failed for 8.4 with exitcode 1 |
…ows (#954) (#957) ci: temporarily disable focal job in merge-queue and nightly flows (#954) Launchpad's PPA infrastructure (ppa.launchpad.net / ppa.launchpadcontent.net) has been intermittently refusing connections for several days, breaking focal's install of gcc-11 from ppa:ubuntu-toolchain-r/test which is required because focal needs gcc-11 for the SVS code path's C++20 features. Comment out the focal job in both event-merge-to-queue.yml and event-nightly.yml (and the corresponding entries in their respective needs: lists) so the merge queue and nightly notifier are not blocked by this upstream outage. focal.yml itself is untouched and remains manually-triggerable via workflow_dispatch. To be reverted once a durable solution (likely a pre-built CI image with gcc-11 baked in, removing the per-run Launchpad dependency) is in place. (cherry picked from commit fe17589)
Describe the changes in the pull request
Comment out the
focaljob (and its correspondingneeds:entry) in bothevent-merge-to-queue.ymlandevent-nightly.yml, so the merge queue and nightly notifier are no longer blocked by Ubuntu 20.04 CI failures.For the past several days, Canonical's PPA edge (
ppa.launchpad.net/ppa.launchpadcontent.net, both resolving to185.125.190.80) has been intermittently refusing connections, causingadd-apt-repository ppa:ubuntu-toolchain-r/testto fail in.install/ubuntu_20.04.sh. We need that PPA because focal's stock GCC is 9, but the SVS code path requires C++20 features that need GCC ≥ 11 (seecmake/svs.cmake). The outage was verified from both the GitHub-hosted runner and a local network, confirming it is upstream and not workflow- or runner-related; no amount of apt retry/timeout/mirror-swap configuration in our workflow can route around it.focal.ymlitself is left untouched and remains manually-triggerable viaworkflow_dispatch, so we can keep iterating on a fix (likely a pre-built CI image withgcc-11baked in to remove the per-run Launchpad dependency) without re-enabling it in any auto-flow. ATODO:comment marks the spot for re-enablement.Which issues this PR fixes
Main objects this PR modified
.github/workflows/event-merge-to-queue.yml—focaljob and its entry inpr-validation.needscommented out..github/workflows/event-nightly.yml—focaljob and its entry innotify-on-failure.needscommented out.Mark if applicable
Note
Low Risk
Low risk: workflow-only change that removes Ubuntu 20.04 (
focal) from required job dependencies, which may reduce CI coverage but does not affect runtime code.Overview
Temporarily comments out the Ubuntu 20.04 (
focal) job inevent-merge-to-queue.ymlandevent-nightly.yml, with a TODO note for re-enabling.Updates the aggregate gating jobs (
pr-validationandnotify-on-failure) to dropfocalfrom theirneeds, so merge-queue validation and nightly notifications no longer wait onfocalresults.Reviewed by Cursor Bugbot for commit 005d600. Bugbot is set up for automated code reviews on this repo. Configure here.