Skip to content

Recover Linux CI gates interrupted by Ubuntu mirror DNS failures #757

Closed as not planned

Description

@jtravs

What happens

On 11 November 2026, PR #611 CI at 118e600c fails multiple Linux jobs before their tests. The native toolchain and runtime-library installation steps cannot resolve azure.archive.ubuntu.com; apt-get update warns and the subsequent package install exits with code 100. Native quality, documentation, coverage, lowest-dependency, slow and Linux GUI gates are affected. Other platforms and native-wheel jobs continue.

Evidence

The native sanitizer job and documentation job both record Temporary failure resolving 'azure.archive.ubuntu.com' for ordinary Ubuntu 24.04 packages. These are observed CI logs, not a locally reproduced code failure. Separate static test-typing failures are tracked in #756.

To do

  • Retry affected jobs after the external resolution failure clears, preserving the original logs.
  • If it repeats, identify a supported runner/package-mirror remedy without skipping installs, checks or dependency provenance.
  • Record successful replacement gate results before marking the implementation ready.

Done when

Every affected mandatory gate executes and passes on the submitted tree. The pre-test failure does not count as a test pass, and this issue does not authorize reducing the matrix.

Related: SEP 48 #608 and implementation #611; Julia job-duration work is separately #712.

Activity

  1. added
    priority: mediumReal work that should not wait long
    testingTests, test tiers and CI coverage
    on Nov 11, 2026
  2. jtravs commented on Nov 12, 2026

    @jtravs
    ContributorAuthor

    PR #611's gate re-run is moot; keep only if the Ubuntu mirror DNS failure recurs on main CI, otherwise close.

  3. jtravs commented on Nov 13, 2026

    @jtravs
    ContributorAuthor

    Closing per the maintainer's note: the affected gates were PR #611's (SEP 48, withdrawn), and the Ubuntu mirror DNS failure has not recurred on main CI. Reopen if it does. (Issue-fixing session triage.)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    priority: mediumReal work that should not wait longtestingTests, test tiers and CI coverage

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions