fix(batch-execute/signal): handle batched execution cancellation · graphql-hive/gateway@85ef635

Triggered via pull request February 20, 2026 16:41

ardatan

synchronize #1928

batch-execution-cancellation

Status Failure

Total duration 42m 48s

Artifacts 1

memtest.yml

on: pull_request

Matrix: memtest

Annotations

8 errors and 4 warnings

node / opentelemetry

Final attempt failed. Child_process exited with error code 1

[memtest] e2e/opentelemetry/opentelemetry.memtest.ts > OpenTelemetry http exporter > should have stable memory usage: internal/perf/src/memtest.ts#L227

AssertionError: Leak detected on 2 object(s) that kept growing in every snapshot: - "Object" allocated 20.42kB, freed 7.40kB (Δ13.02kB) - 435 instances were added, 179 were removed (Δ256) - "(number)" allocated 18.74kB, freed 14.90kB (Δ3.84kB) - 1171 instances were added, 931 were removed (Δ240) Please load the following heap snapshots respectively in Chrome DevTools for more details: 1. e2e/opentelemetry/loadtest-nblz-idle-run-1-2026-02-20T17-19-08.heapsnapshot 2. e2e/opentelemetry/loadtest-nblz-calmdown-run-1-2026-02-20T17-19-08.heapsnapshot 3. e2e/opentelemetry/loadtest-nblz-calmdown-run-2-2026-02-20T17-19-08.heapsnapshot 4. e2e/opentelemetry/loadtest-nblz-calmdown-run-3-2026-02-20T17-19-08.heapsnapshot 5. e2e/opentelemetry/loadtest-nblz-calmdown-run-4-2026-02-20T17-19-08.heapsnapshot 6. e2e/opentelemetry/loadtest-nblz-calmdown-run-5-2026-02-20T17-19-08.heapsnapshot ❯ internal/perf/src/memtest.ts:227:18

[memtest] e2e/opentelemetry/opentelemetry.memtest.ts > OpenTelemetry grpc exporter > should have stable memory usage: internal/perf/src/memtest.ts#L227

AssertionError: Leak detected on 2 object(s) that kept growing in every snapshot: - "Object" allocated 27.36kB, freed 11.30kB (Δ16.06kB) - 430 instances were added, 153 were removed (Δ277) - "(number)" allocated 8.21kB, freed 6.48kB (Δ1.73kB) - 513 instances were added, 405 were removed (Δ108) Please load the following heap snapshots respectively in Chrome DevTools for more details: 1. e2e/opentelemetry/loadtest-ex2z-idle-run-1-2026-02-20T17-15-18.heapsnapshot 2. e2e/opentelemetry/loadtest-ex2z-calmdown-run-1-2026-02-20T17-15-18.heapsnapshot 3. e2e/opentelemetry/loadtest-ex2z-calmdown-run-2-2026-02-20T17-15-18.heapsnapshot 4. e2e/opentelemetry/loadtest-ex2z-calmdown-run-3-2026-02-20T17-15-18.heapsnapshot 5. e2e/opentelemetry/loadtest-ex2z-calmdown-run-4-2026-02-20T17-15-18.heapsnapshot 6. e2e/opentelemetry/loadtest-ex2z-calmdown-run-5-2026-02-20T17-15-18.heapsnapshot ❯ internal/perf/src/memtest.ts:227:18

[memtest] e2e/opentelemetry/opentelemetry.memtest.ts > OpenTelemetry http exporter > should have stable memory usage: internal/perf/src/memtest.ts#L227

AssertionError: Leak detected on 2 object(s) that kept growing in every snapshot: - "Object" allocated 19.46kB, freed 6.74kB (Δ12.72kB) - 422 instances were added, 171 were removed (Δ251) - "(number)" allocated 18.67kB, freed 14.85kB (Δ3.82kB) - 1167 instances were added, 928 were removed (Δ239) Please load the following heap snapshots respectively in Chrome DevTools for more details: 1. e2e/opentelemetry/loadtest-d832-idle-run-1-2026-02-20T17-11-09.heapsnapshot 2. e2e/opentelemetry/loadtest-d832-calmdown-run-1-2026-02-20T17-11-09.heapsnapshot 3. e2e/opentelemetry/loadtest-d832-calmdown-run-2-2026-02-20T17-11-09.heapsnapshot 4. e2e/opentelemetry/loadtest-d832-calmdown-run-3-2026-02-20T17-11-09.heapsnapshot 5. e2e/opentelemetry/loadtest-d832-calmdown-run-4-2026-02-20T17-11-09.heapsnapshot 6. e2e/opentelemetry/loadtest-d832-calmdown-run-5-2026-02-20T17-11-09.heapsnapshot ❯ internal/perf/src/memtest.ts:227:18

[memtest] e2e/opentelemetry/opentelemetry.memtest.ts > OpenTelemetry grpc exporter > should have stable memory usage: internal/perf/src/memtest.ts#L227

AssertionError: Leak detected on 1 object(s) that kept growing in every snapshot: - "Object" allocated 30.66kB, freed 13.38kB (Δ17.28kB) - 481 instances were added, 189 were removed (Δ292) Please load the following heap snapshots respectively in Chrome DevTools for more details: 1. e2e/opentelemetry/loadtest-73kv-idle-run-1-2026-02-20T16-59-13.heapsnapshot 2. e2e/opentelemetry/loadtest-73kv-calmdown-run-1-2026-02-20T16-59-13.heapsnapshot 3. e2e/opentelemetry/loadtest-73kv-calmdown-run-2-2026-02-20T16-59-13.heapsnapshot 4. e2e/opentelemetry/loadtest-73kv-calmdown-run-3-2026-02-20T16-59-13.heapsnapshot 5. e2e/opentelemetry/loadtest-73kv-calmdown-run-4-2026-02-20T16-59-13.heapsnapshot 6. e2e/opentelemetry/loadtest-73kv-calmdown-run-5-2026-02-20T16-59-13.heapsnapshot ❯ internal/perf/src/memtest.ts:227:18

[memtest] e2e/opentelemetry/opentelemetry.memtest.ts > OpenTelemetry http exporter > should have stable memory usage: internal/perf/src/memtest.ts#L227

AssertionError: Leak detected on 1 object(s) that kept growing in every snapshot: - "(object shape)" allocated 233.10kB, freed 162.85kB (Δ70.26kB) - 1113 instances were added, 515 were removed (Δ598) Please load the following heap snapshots respectively in Chrome DevTools for more details: 1. e2e/opentelemetry/loadtest-4ygc-idle-run-1-2026-02-20T16-54-59.heapsnapshot 2. e2e/opentelemetry/loadtest-4ygc-calmdown-run-1-2026-02-20T16-54-59.heapsnapshot 3. e2e/opentelemetry/loadtest-4ygc-calmdown-run-2-2026-02-20T16-54-59.heapsnapshot 4. e2e/opentelemetry/loadtest-4ygc-calmdown-run-3-2026-02-20T16-54-59.heapsnapshot 5. e2e/opentelemetry/loadtest-4ygc-calmdown-run-4-2026-02-20T16-54-59.heapsnapshot 6. e2e/opentelemetry/loadtest-4ygc-calmdown-run-5-2026-02-20T16-54-59.heapsnapshot ❯ internal/perf/src/memtest.ts:227:18

[memtest] e2e/opentelemetry/opentelemetry.memtest.ts > OpenTelemetry grpc exporter > should have stable memory usage: internal/perf/src/memtest.ts#L227

AssertionError: Leak detected on 2 object(s) that kept growing in every snapshot: - "Object" allocated 28.68kB, freed 11.75kB (Δ16.93kB) - 447 instances were added, 160 were removed (Δ287) - "(number)" allocated 8.19kB, freed 6.27kB (Δ1.92kB) - 512 instances were added, 392 were removed (Δ120) Please load the following heap snapshots respectively in Chrome DevTools for more details: 1. e2e/opentelemetry/loadtest-k52e-idle-run-1-2026-02-20T16-51-07.heapsnapshot 2. e2e/opentelemetry/loadtest-k52e-calmdown-run-1-2026-02-20T16-51-07.heapsnapshot 3. e2e/opentelemetry/loadtest-k52e-calmdown-run-2-2026-02-20T16-51-07.heapsnapshot 4. e2e/opentelemetry/loadtest-k52e-calmdown-run-3-2026-02-20T16-51-07.heapsnapshot 5. e2e/opentelemetry/loadtest-k52e-calmdown-run-4-2026-02-20T16-51-07.heapsnapshot 6. e2e/opentelemetry/loadtest-k52e-calmdown-run-5-2026-02-20T16-51-07.heapsnapshot ❯ internal/perf/src/memtest.ts:227:18

[memtest] e2e/opentelemetry/opentelemetry.memtest.ts > OpenTelemetry http exporter > should have stable memory usage: internal/perf/src/memtest.ts#L227

AssertionError: Leak detected on 2 object(s) that kept growing in every snapshot: - "Object" allocated 20.62kB, freed 7.23kB (Δ13.38kB) - 436 instances were added, 178 were removed (Δ258) - "(number)" allocated 18.80kB, freed 14.94kB (Δ3.86kB) - 1175 instances were added, 934 were removed (Δ241) Please load the following heap snapshots respectively in Chrome DevTools for more details: 1. e2e/opentelemetry/loadtest-mq6r-idle-run-1-2026-02-20T16-47-01.heapsnapshot 2. e2e/opentelemetry/loadtest-mq6r-calmdown-run-1-2026-02-20T16-47-01.heapsnapshot 3. e2e/opentelemetry/loadtest-mq6r-calmdown-run-2-2026-02-20T16-47-01.heapsnapshot 4. e2e/opentelemetry/loadtest-mq6r-calmdown-run-3-2026-02-20T16-47-01.heapsnapshot 5. e2e/opentelemetry/loadtest-mq6r-calmdown-run-4-2026-02-20T16-47-01.heapsnapshot 6. e2e/opentelemetry/loadtest-mq6r-calmdown-run-5-2026-02-20T16-47-01.heapsnapshot ❯ internal/perf/src/memtest.ts:227:18

node / opentelemetry

Attempt 4 failed. Reason: Child_process exited with error code 1

node / opentelemetry

Attempt 3 failed. Reason: Child_process exited with error code 1

node / opentelemetry

Attempt 2 failed. Reason: Child_process exited with error code 1

node / opentelemetry

Attempt 1 failed. Reason: Child_process exited with error code 1