Parent Log: http://ci.aztec-labs.com/a0a5ca8d8b3bb5c7 Command: f643ae060f517c84 yarn-project/scripts/run_test.sh simulator/src/public/state_manager/nullifiers.test.ts Commit: https://github.com/AztecProtocol/aztec-packages/commit/be78cf2e908c8f2f34676d72c74c8b92a3f591d1 Env: REF_NAME=release-please--branches--next CURRENT_VERSION=0.88.0 CI_FULL=0 Date: Fri Jun 20 23:00:18 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 23:00:19 PASS src/public/state_manager/nullifiers.test.ts 23:00:19 avm nullifier caching 23:00:19 Nullifier caching and existence checks 23:00:19 ✓ Reading a non-existent nullifier works (gets zero & DNE) (5 ms) 23:00:19 ✓ Should cache nullifier, existence check works after creation (1 ms) 23:00:19 ✓ Existence check works on fallback to host (gets index, exists, not-pending) (1 ms) 23:00:19 ✓ Existence check works on fallback to parent (gets value, exists, is pending) (1 ms) 23:00:19 ✓ Existence check works on fallback to grandparent (gets value, exists, is pending) (1 ms) 23:00:19 Nullifier collision failures 23:00:19 ✓ Cant append nullifier that already exists in cache (7 ms) 23:00:19 ✓ Cant append nullifier that already exists in parent cache (1 ms) 23:00:19 ✓ Cant append nullifier that already exist in host (1 ms) 23:00:19 Nullifier cache merging 23:00:19 ✓ Should be able to merge two nullifier caches together (1 ms) 23:00:19 ✓ Cant merge two nullifier caches with colliding entries (2 ms) 23:00:19 23:00:19 Test Suites: 1 passed, 1 total 23:00:19 Tests: 10 passed, 10 total 23:00:19 Snapshots: 0 total 23:00:19 Time: 0.421 s 23:00:19 Ran all test suites matching simulator/src/public/state_manager/nullifiers.test.ts. 23:00:19 Force exiting Jest: Have you considered using `--detectOpenHandles` to detect async operations that kept running after all tests finished?