Repository navigation
ci: run AddressSanitizer and fuzzing nightly - #3029
Merged
Merged
Conversation
matdexir
temporarily deployed
to
cluster-ci-benchmark
October 23, 2026 13:40 — with
GitHub Actions
Inactive
matdexir
temporarily deployed
to
cluster-ci-benchmark
October 23, 2026 13:40 — with
GitHub Actions
Inactive
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
matdexir
temporarily deployed
to
cluster-ci-benchmark
October 23, 2026 13:57 — with
GitHub Actions
Inactive
matdexir
temporarily deployed
to
cluster-ci-benchmark
October 23, 2026 14:01 — with
GitHub Actions
Inactive
matdexir
temporarily deployed
to
cluster-ci-benchmark
October 23, 2026 14:01 — with
GitHub Actions
Inactive
Contributor
Author
|
the CI/Nix/Build shared nix package is unrelated to this change and it's flaky, i shall try to make it consistent. |
matdexir
marked this pull request as ready for review
October 23, 2026 14:04
matdexir
temporarily deployed
to
cluster-ci-benchmark
October 23, 2026 14:06 — with
GitHub Actions
Inactive
matdexir
temporarily deployed
to
cluster-ci-benchmark
October 23, 2026 14:06 — with
GitHub Actions
Inactive
matdexir
temporarily deployed
to
cluster-ci-benchmark
October 23, 2026 16:03 — with
GitHub Actions
Inactive
matdexir
temporarily deployed
to
cluster-ci-benchmark
October 23, 2026 16:03 — with
GitHub Actions
Inactive
Both lanes are expensive and do not gate merge. Pull requests keep the Nix Bazel lane.
The retained client returns EPERM when a sandboxed build chmods that source, so uncached package builds fail before compile.
This reverts commit fac81a3.
A published release should get the same sanitizer and fuzz signal as the nightly run. The tag stays on the read-only cache key.
matdexir
force-pushed
the
nightly-asan-fuzz
branch
from
October 23, 2026 16:05
4a298fa to
9ea293a
Compare
matdexir
temporarily deployed
to
cluster-ci-benchmark
October 23, 2026 16:05 — with
GitHub Actions
Inactive
A release pull request, such as release/v1.8.1, should get the same sanitizer and fuzz signal as a published release. Ordinary pull requests stay on the Nix Bazel lane.
matdexir
temporarily deployed
to
cluster-ci-benchmark
October 23, 2026 16:07 — with
GitHub Actions
Inactive
matdexir
temporarily deployed
to
cluster-ci-benchmark
October 23, 2026 16:09 — with
GitHub Actions
Inactive
MarcusSorealheis
temporarily deployed
to
cluster-ci-benchmark
October 23, 2026 21:38 — with
GitHub Actions
Inactive
MarcusSorealheis
temporarily deployed
to
cluster-ci-benchmark
October 23, 2026 21:38 — with
GitHub Actions
Inactive
1 of 4 tasks
This branch was successfully deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What and why
AddressSanitizer and ClusterFuzzLite were running on pull requests. Both are expensive and neither gates merge, so ordinary pull requests now keep the Nix Bazel lane. These two still run at 07:00 UTC against main, when a release is published, when someone starts the workflow by hand, and on a release pull request. A release pull request is one whose head branch is
release/vX.Y.Z(as in #3028) or whose title isRelease NativeLink vX.Y.Z.How was this verified?
Compared the workflow triggers with the existing nightly lanes (Cargo Native, Coverage) and with the signed-artifacts workflow, which also uses
release: types: [published]. Release pull requests follow therelease/vX.Y.Zbranch used by #3028 and byRelease / Prepare PR. Confirmed the branch ruleset does not require theasan / ubuntu-24.04orFuzzchecks. Did not dispatch either workflow; the schedule and the release trigger only start once this is on main. This pull request itself is not a release pull request, so those two jobs should skip here.Risk
Low. A sanitizer or fuzzer failure shows up the next morning, on a release pull request, on the next published release, or on a manual run, rather than on an ordinary pull request. A release pull request and a published release stay on the read-only cache key. A manual run of a branch other than main does too. The nightly run of main still uses the write key.
AI assistance
An agent wrote the workflow edits. I reviewed the approach and asked for this pull request.