Parent Log:
http://ci.aztec-labs.com/6fb11eab795b5361
Command: 9da14e8553889f6a:ISOLATE=1:CPUS=8:NAME=client_flows/bridging BENCHMARK_CONFIG=key_flows LOG_LEVEL=error BENCH_OUTPUT=bench-out/ yarn-project/end-to-end/scripts/run_test.sh simple client_flows/bridging
Commit:
https://github.com/AztecProtocol/aztec-packages/commit/81bcc3b7a49c7a4b894343833bb4f5c6329ef9bf
Env: REF_NAME=gh-readonly-queue/next/pr-14459-e8582b21dde365dda59357b5295dc4796ed0be00 CURRENT_VERSION=0.87.3 CI_FULL=1
Date: Tue May 27 17:44:25 UTC 2025
System: ARCH=amd64 CPUS=128 MEM=493Gi HOSTNAME=gh-readonly-queue_next_pr-14459-e8582b21dde365dda5_amd64_x2-full
Resources: CPU_LIST=32,33,34,35,36,37,38,39 CPUS=8 MEM=32g TIMEOUT=600s
History:
http://ci.aztec-labs.com/list/f3cbe5baa41f7dc0
17:44:25 +++ id -u
17:44:25 +++ id -g
17:44:25 ++ docker run -d --name client_flows_bridging --net=none --cpuset-cpus=32,33,34,35,36,37,38,39 --cpus=8 --memory=32g --user 1000:1000 -v/home/aztec-dev:/home/aztec-dev --mount type=tmpfs,target=/tmp,tmpfs-size=1g --workdir /home/aztec-dev/aztec-packages -e HOME -e VERBOSE -e GIT_CONFIG_GLOBAL=/home/aztec-dev/aztec-packages/build-images/src/home/.gitconfig -e FORCE_COLOR=true -e CPUS -e MEM aztecprotocol/build:3.0 /bin/bash -c 'timeout -v 600s bash -c '\''BENCHMARK_CONFIG=key_flows LOG_LEVEL=error BENCH_OUTPUT=bench-out/ yarn-project/end-to-end/scripts/run_test.sh simple client_flows/bridging'\'''
17:44:25 + cid=55cabbe3c1da97ae9ba7e0ceb086e871f6e404db0ec095c6bc0c474631127e9a
17:44:25 + set +x
17:49:30
FAIL src/bench/client_flows/bridging.test.ts (
303.945 s)
17:49:30
● Bridging benchmark › Bridging benchmark for ecdsar1 › ecdsar1 contract bridges tokens from L1 claiming privately, pays using sponsored_fpc
17:49:30
17:49:30 thrown: "Exceeded timeout of 300000 ms for a hook.
17:49:30 Add a timeout value to this test to increase the timeout, if this is a long-running test. See
https://jestjs.io/docs/api#testname-fn-timeout."
17:49:30
17:49:30
26 | const config
= t
.config
.bridging
;
17:49:30
27 |
17:49:30
> 28 | beforeAll(async () => {
17:49:30
| ^
17:49:30
29 | await t.applyBaseSnapshots();
17:49:30
30 | await t.applyDeployBananaTokenSnapshot();
17:49:30
31 | await t.applyFPCSetupSnapshot();
17:49:30
17:49:30
at beforeAll (bench/client_flows/bridging.test.ts:28:3)
17:49:30
at describe (bench/client_flows/bridging.test.ts:15:1)
17:49:30
17:49:30
17:49:30
● Test suite failed to run
17:49:30
17:49:30 TypeError: Cannot read properties of undefined (reading 'stop')
17:49:30
17:49:30
152 |
17:49:30
153 | async teardown() {
17:49:30
> 154 | this.chainMonitor
.stop()
;
17:49:30
| ^
17:49:30
155 | await this.snapshotManager
.teardown()
;
17:49:30
156 | }
17:49:30
157 |
17:49:30
17:49:30
at ClientFlowsBenchmark.stop [as teardown] (bench/client_flows/client_flows_benchmark.ts
:154:23)
17:49:30
at Object.teardown (bench/client_flows/bridging.test.ts
:37:13)
17:49:30
17:49:30
Test Suites: 1 failed, 1 total
17:49:30
Tests: 1 failed, 1 total
17:49:30
Snapshots: 0 total
17:49:30
Time: 303.996 s
17:49:30
Ran all test suites matching /client_flows\/bridging/i
.
17:49:30
Force exiting Jest: Have you considered using `--detectOpenHandles` to detect async operations that kept running after all tests finished?