Parent Log: http://ci.aztec-labs.com/5a5d3e4dc8dea85f Command: a01b491a8c032117 yarn-project/scripts/run_test.sh stdlib/src/kernel/hints/find_private_kernel_reset_dimensions.test.ts Commit: https://github.com/AztecProtocol/aztec-packages/commit/60e60f99f2634ad75a76b6e103858ff9ccd041d5 Env: REF_NAME=gh-readonly-queue/next/pr-15081-58b067708e8ff927bf26b2994203134853a7eb71 CURRENT_VERSION=0.87.6 CI_FULL=1 Date: Mon Jun 16 18:29:51 UTC 2025 System: ARCH=amd64 CPUS=128 MEM=493Gi HOSTNAME=pr-15081_amd64_x3-full Resources: CPU_LIST=0-127 CPUS=2 MEM=8g TIMEOUT=600s History: http://ci.aztec-labs.com/list/history_40ef5b8a809c97c5_next 18:29:53 PASS src/kernel/hints/find_private_kernel_reset_dimensions.test.ts 18:29:53 findPrivateKernelResetDimensions 18:29:53 only variant 18:29:53 returns smallest dimensions by default (5 ms) 18:29:53 finds the cheapest option for all dimensions (1 ms) 18:29:53 finds the cheapest option for partial dimensions (1 ms) 18:29:53 with standalone 18:29:53 uses standalone for one dimension 18:29:53 uses variant for one dimension if standalone is more expensive 18:29:53 with special cases 18:29:53 returns smallest special case by default 18:29:53 returns the option to reset all dimensions 18:29:53 picks cheapest option among variants 18:29:53 picks cheapest option among standalone 18:29:53 is inner 18:29:53 returns the option that does not perform siloing 18:29:53 allow remainder 18:29:53 finds the option that can reset the most values (14 ms) 18:29:53 finds the option in special cases that can reset the most values (1 ms) 18:29:53 18:29:53 Test Suites: 1 passed, 1 total 18:29:53 Tests: 12 passed, 12 total 18:29:53 Snapshots: 0 total 18:29:53 Time: 0.589 s 18:29:53 Ran all test suites matching stdlib/src/kernel/hints/find_private_kernel_reset_dimensions.test.ts. 18:29:53 Force exiting Jest: Have you considered using `--detectOpenHandles` to detect async operations that kept running after all tests finished?