Skip to content

Conversation

@vezenovm
Copy link
Contributor

DO NOT MERGE

Testing out reverting noir-lang/noir#9987 as I am getting a passing lest locally.

@AztecBot
Copy link
Collaborator

Flakey Tests

🤖 says: This CI run detected 1 tests that failed, but were tolerated due to a .test_patterns.yml entry.

\033FLAKED\033 (8;;http://ci.aztec-labs.com/d0b1ee8af6453c94�d0b1ee8af6453c948;;�):  yarn-project/end-to-end/scripts/run_test.sh simple src/e2e_epochs/epochs_manual_rollback.test.ts (87s) (code: 1) group:e2e-p2p-epoch-flakes (\033Maxim Vezenov\033: missing always)

github-merge-queue bot pushed a commit that referenced this pull request Jan 27, 2026
…c-up bootstrap (#19945)

If I want to test a patch in the Noir submodule against CI by altering
`noir/noir-repo` directly rather than needing a new temporary tag it is
currently not possible.

When aztec-up [fetchs the
versions](https://github.com/AztecProtocol/aztec-packages/blob/0bee1eb2dba5ed7d0b88466ae8ab58b9177dceb1/aztec-up/bootstrap.sh#L8)
the `noir_version` expects an exact match for the tag.

This prevents being able to directly modify the submodule as no tag
exists. I ran into this issue in
#19871 where CI
would fail with `fatal: no tag exactly matches
'515b2702975fd85069fae48ddd0d90a56cd65628'` at `aztec-up/bootstrap.sh`.
This does not affect release builds as those are also protected in the
[Noir
build](https://github.com/AztecProtocol/aztec-packages/blob/f94d8e86e88ad812c50a2661f63fedc30c59a04b/noir/bootstrap.sh#L98).
@vezenovm
Copy link
Contributor Author

Closing as tests are passing

@vezenovm vezenovm closed this Jan 28, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants