Skip to content

chore!: update constant hash values#20257

Merged
LeilaWang merged 1 commit intonextfrom
lw/constant_hash
Feb 9, 2026
Merged

chore!: update constant hash values#20257
LeilaWang merged 1 commit intonextfrom
lw/constant_hash

Conversation

@LeilaWang
Copy link
Contributor

  • Domain separator: hash("az_dom_sep__name") as u32
  • Constants used in protocol circuits: hash("az_pc__name")
  • Constants used in aztec-nr: hash("az_nr__name")

@LeilaWang LeilaWang changed the title chore: update constant hash values chore!: update constant hash values Feb 6, 2026
@LeilaWang LeilaWang force-pushed the lw/constant_hash branch 3 times, most recently from bcfa646 to d6397cf Compare February 9, 2026 11:20
@AztecBot
Copy link
Collaborator

AztecBot commented Feb 9, 2026

Flakey Tests

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

\033FLAKED\033 (8;;http://ci.aztec-labs.com/db1122af19bf0522�db1122af19bf05228;;�): yarn-project/scripts/run_test.sh p2p/src/client/test/p2p_client.integration_message_propagation.test.ts (23s) (code: 1) group:e2e-p2p-epoch-flakes
\033FLAKED\033 (8;;http://ci.aztec-labs.com/f30aa7f135837678�f30aa7f1358376788;;�):  yarn-project/end-to-end/scripts/run_test.sh simple src/e2e_p2p/gossip_network.test.ts (382s) (code: 1) group:e2e-p2p-epoch-flakes

Copy link
Contributor

@iAmMichaelConnor iAmMichaelConnor left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

(Approving, so that I don't block you once you resolve any comments)

- Domain separator: `hash("az_dom_sep__name") as u32`
- Constants used in protocol circuits: `hash("az_pc__name")`
- Constants used in aztec-nr: `hash("az_nr__name")`
@LeilaWang LeilaWang added this pull request to the merge queue Feb 9, 2026
Merged via the queue into next with commit 79c417b Feb 9, 2026
19 checks passed
@LeilaWang LeilaWang deleted the lw/constant_hash branch February 9, 2026 15:52
ludamad added a commit that referenced this pull request Feb 23, 2026
Slide 19 (§4 insights · PR correlation): two-column layout showing which
PRs caused each weekly flake spike and which fixes produced each recovery:

Spikes:
- W02 (2,647 flakes): Santiago refactors #19532/#19509/#19564 exposed
  timing races across p2p/epoch simultaneously
- W04 (935 flakes): PhilWindle #19982 added cross-chain mbps tests
  without pre-deflaking — valid_epoch_pruned_slash 0→346 events
- W06 (850 flakes): three high-risk PRs merged same day (#20047 peer
  scoring, #20241 max checkpoints→32, #20257 hash constants)

Fixes:
- W03 recovery: Santiago #19914 — checkpointed chain tip for PXE
  (root fix; PXE was using latest not checkpointed block)
- W05 recovery: Santiago #20088 slasher multi-block fix + #20140
  discv5 deflake + GCP step-down (−6 testbed namespaces)
- W07 improvement: Santiago #20351 mbps fix (p2p_client 311→0),
  #20462 remove hardcoded 10s timeout, ludamad #20613 CI parallelism

Also: correct three factual errors spotted during full review —
- Summary: next P50 is growing (+10% in 3 weeks), not stable
- Flake trend W07 note: e2e-p2p-epoch-flakes dropped 373×, not just
  "251 flakes lowest since December"
- Gaps slide: replaced stale "ci_phases broken" card with GCP egress
  costs gap (bc→awk fix is deployed; egress attribution is the gap now)
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