Parent Log: http://ci.aztec-labs.com/820a0bb63168d9da Command: b895a7fa8f839b60 yarn-project/scripts/run_test.sh simulator/src/public/state_manager/nullifiers.test.ts Commit: https://github.com/AztecProtocol/aztec-packages/commit/408ec6f57f38faf5e1dbdf7712a82e2e1112be2c Env: REF_NAME=release-please--branches--next CURRENT_VERSION=0.88.0 CI_FULL=0 Date: Sat Jun 14 11:24:39 UTC 2025 System: ARCH=amd64 CPUS=128 MEM=493Gi HOSTNAME=release-please--branches--next_amd64 Resources: CPU_LIST=0-127 CPUS=2 MEM=8g TIMEOUT=600s History: http://ci.aztec-labs.com/list/history_408002b51fade386_next 11:24:41 PASS src/public/state_manager/nullifiers.test.ts 11:24:41 avm nullifier caching 11:24:41 Nullifier caching and existence checks 11:24:41 Reading a non-existent nullifier works (gets zero & DNE) (7 ms) 11:24:41 Should cache nullifier, existence check works after creation (1 ms) 11:24:41 Existence check works on fallback to host (gets index, exists, not-pending) (1 ms) 11:24:41 Existence check works on fallback to parent (gets value, exists, is pending) (1 ms) 11:24:41 Existence check works on fallback to grandparent (gets value, exists, is pending) 11:24:41 Nullifier collision failures 11:24:41 Cant append nullifier that already exists in cache (6 ms) 11:24:41 Cant append nullifier that already exists in parent cache (1 ms) 11:24:41 Cant append nullifier that already exist in host (1 ms) 11:24:41 Nullifier cache merging 11:24:41 Should be able to merge two nullifier caches together (1 ms) 11:24:41 Cant merge two nullifier caches with colliding entries (1 ms) 11:24:41 11:24:41 Test Suites: 1 passed, 1 total 11:24:41 Tests: 10 passed, 10 total 11:24:41 Snapshots: 0 total 11:24:41 Time: 0.519 s 11:24:41 Ran all test suites matching /simulator\/src\/public\/state_manager\/nullifiers.test.ts/i. 11:24:41 Force exiting Jest: Have you considered using `--detectOpenHandles` to detect async operations that kept running after all tests finished?