Parent Log: http://ci.aztec-labs.com/8c7fab2989a37396 Command: a668859b212fc7b1 yarn-project/scripts/run_test.sh stdlib/src/kernel/private_kernel_tail_circuit_public_inputs.test.ts Commit: https://github.com/AztecProtocol/aztec-packages/commit/6c74ed65f1d93cd2cb1d0bc305917b967dd0f83a Env: REF_NAME=release-please--branches--next CURRENT_VERSION=0.88.0 CI_FULL=0 Date: Tue Jun 17 22:22:41 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_dcd95c9839dbaf63_next 22:22:44 PASS src/kernel/private_kernel_tail_circuit_public_inputs.test.ts 22:22:44 PrivateKernelTailCircuitPublicInputs 22:22:44 ✓ Data for public after serialization and deserialization is equal to the original (50 ms) 22:22:44 ✓ Data for rollup after serialization and deserialization is equal to the original (18 ms) 22:22:44 22:22:44 Test Suites: 1 passed, 1 total 22:22:44 Tests: 2 passed, 2 total 22:22:44 Snapshots: 0 total 22:22:44 Time: 1.56 s 22:22:44 Ran all test suites matching stdlib/src/kernel/private_kernel_tail_circuit_public_inputs.test.ts. 22:22:44 Force exiting Jest: Have you considered using `--detectOpenHandles` to detect async operations that kept running after all tests finished?