chore: remove protocol fuzzer - #25057
Merged
Merged
Conversation
Collaborator
Flakey Tests🤖 says: This CI run detected 1 tests that failed, but were tolerated due to a .test_patterns.yml entry. |
nventuro
approved these changes
Jul 29, 2026
fcarreiro
added a commit
that referenced
this pull request
Aug 3, 2026
Part of simplification towards the monorepo split. This is not regularly used. It can be brought back if needed. If you every DO bring it back, note that you DO NOT NEED THE AVM TRANSPILER. The code can be adapted so that it uses `bb aztec_process` instead, which executes the transpiler internally (statically linked).
nchamo
pushed a commit
that referenced
this pull request
Aug 3, 2026
Port of #25057 and #25047 to `merge-train/fairies`, cherry-picked in the order they landed on the labs line (0f8d8ad, then b556724). Both picks are line-identical to the originals; the conflicts were only against fairies-side context. - #25057 removes the protocol fuzzer (`noir-projects/labs/protocol-fuzzer/` and its format-check/pre-commit hook entries). - #25047 makes labs-side components (`noir-projects/labs`, `boxes`, `docs`, `aztec-up`, parts of `yarn-project` tests) take their `bb`/`nargo`/`noir-profiler`/`bb-avm`/`acvm` binaries from `labs-aztec-toolchain/bin` instead of reaching into the monorepo build trees directly. On the monorepo the toolchain bootstrap symlinks to the existing build outputs, so nothing is rebuilt or downloaded. Closes https://linear.app/aztec-labs/issue/A-1559/backport-prs-to-next .
fcarreiro
added a commit
that referenced
this pull request
Aug 4, 2026
Merges `next` (b00c780) into `monorepo-split/labs`. > [!IMPORTANT] > This is a branch-sync merge — it should be merged with a **merge commit**, not squashed, so the shared history with `next` is preserved. ## Conflict resolutions Four files conflicted, all in territory where `next` just received the port of #25047/#25057 (via #25078) while labs had already evolved past it: - **`labs-aztec-toolchain/bootstrap.sh` + `README.md`** (add/add): took the labs side. `next`'s version is byte-identical to labs at #25047; labs has since moved to the download-based toolchain (#25049), which supersedes it. - **`noir-projects/labs/bootstrap.sh`**: took the labs side. Both sides carried the same #25047 changes (toolchain nargo path, protocol-fuzzer removal); labs additionally has the targeted partial-clone cache eviction, which is labs-specific (`protocol_types` resolves from a large aztec-packages git clone). - **`Makefile`**: - kept labs' commented-out `# labs-aztec-toolchain: noir bb-cpp-native` (labs already fulfilled `next`'s "comment this out when pinning binaries" TODO) and labs' TODO wording on the format-check dependency; - took `next`'s new `fnd-release` / `fnd-release-tests` targets; - took `next`'s split of `yarn-project:` deps into `noir-projects-labs labs-aztec-toolchain` plus the monorepo-extras line (total dependency set unchanged). ## Toolchain fix (semantic conflict caught by CI) The first CI run failed compiling `account/schnorr_initializerless_account_contract`: two `Return variable contains a constant value` errors pointing at the aztec-nr macro's `self.context.finish()`. Root cause: `next` switched the noir-contracts compile to `--deny-warnings`, relying on the macro-generated `#[allow(constant_return)]` to silence that one lint (replacing the old grep-allowlist in `bootstrap.sh`). Support for `#[allow(constant_return)]` only exists in Noir **v1.0.0-beta.26** — earlier compilers silently ignore the attribute and the warning becomes an error. The labs toolchain provisions the **pinned** noir release, and the pin was still `1.0.0-beta.25`, so CI compiled with a nargo that can't honor the allow. (Both parents were green: labs still had the grep-allowlist, and `next` builds nargo from its beta.26 submodule.) Fix, folded into the merge commit: - bumped `NOIR_VERSION` to `1.0.0-beta.26` in `labs-aztec-toolchain/bootstrap.sh` — reproduced the failure locally with the pinned beta.25 toolchain (identical toolchain hash `0d18d107bf07e280` to the CI run) and verified the same compile passes after the bump; - added `bootstrap.sh` itself to the toolchain `hash` function, so pin bumps and provisioning-logic changes move the cache key even before binaries are refreshed. Note: `BB_VERSION` stays at `6.0.0-nightly.20260729`, which was built against noir `75061fab` — two commits shy of the beta.26 tag (release stamp + an unrelated frontend fix), so the pairing skew is negligible. A future pin refresh can realign both to a newer nightly. ## Notes - Adopts `next`'s noir submodule bump to `40d6574f85` (v1.0.0-beta.26) — verified the pointer matches `origin/next` exactly. - Verified no conflict markers remain (`git diff --check` + full grep) and `make -n` passes for `fast full bench release yarn-project fnd-release-tests noir-projects`. - Supersedes the older sync attempt on `nchamo/labs-next-merge` (f0b50f9), which predates `next`'s current tip.
rangozd
pushed a commit
to rangozd/aztec-packages
that referenced
this pull request
Aug 5, 2026
BEGIN_COMMIT_OVERRIDE chore: port of AztecProtocol#25057 and AztecProtocol#25047 to next (AztecProtocol#25078) chore: split make targets into foundation and labs (AztecProtocol#25079) END_COMMIT_OVERRIDE
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
3 participants
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.
Part of simplification towards the monorepo split.
This is not regularly used. It can be brought back if needed. If you every DO bring it back, note that you DO NOT NEED THE AVM TRANSPILER. The code can be adapted so that it uses
bb aztec_processinstead, which executes the transpiler internally (statically linked).