Skip to content

feat: Node.js Middleware support #2366

feat: Node.js Middleware support

feat: Node.js Middleware support #2366

Triggered via pull request August 20, 2025 19:18
Status Failure
Total duration 1h 4m 32s
Artifacts 12

run-tests.yml

on: pull_request
Matrix: e2e
Matrix: smoke
Matrix: test
Matrix: merge-reports
Fit to window
Zoom out
Zoom in

Annotations

6 errors and 16 notices
test (2, ubuntu-latest, canary)
Process completed with exit code 1.
test (2, windows-2025, canary)
Process completed with exit code 1.
test (3, windows-2025, canary)
Process completed with exit code 1.
test (1, windows-2025, canary)
Process completed with exit code 1.
test (2, ubuntu-latest, latest)
Process completed with exit code 1.
test (2, windows-2025, latest)
Process completed with exit code 1.
test (2, windows-2025, canary)
Windows-2025 runners will change the working directory to a new D:/ drive beginning on 2025-08-18. For more details see https://github.com/actions/runner-images/issues/12744.
test (3, windows-2025, canary)
Windows-2025 runners will change the working directory to a new D:/ drive beginning on 2025-08-18. For more details see https://github.com/actions/runner-images/issues/12744.
test (1, windows-2025, canary)
Windows-2025 runners will change the working directory to a new D:/ drive beginning on 2025-08-18. For more details see https://github.com/actions/runner-images/issues/12744.
test (5, windows-2025, latest)
Windows-2025 runners will change the working directory to a new D:/ drive beginning on 2025-08-18. For more details see https://github.com/actions/runner-images/issues/12744.
test (3, windows-2025, latest)
Windows-2025 runners will change the working directory to a new D:/ drive beginning on 2025-08-18. For more details see https://github.com/actions/runner-images/issues/12744.
test (1, windows-2025, latest)
Windows-2025 runners will change the working directory to a new D:/ drive beginning on 2025-08-18. For more details see https://github.com/actions/runner-images/issues/12744.
test (8, windows-2025, latest)
Windows-2025 runners will change the working directory to a new D:/ drive beginning on 2025-08-18. For more details see https://github.com/actions/runner-images/issues/12744.
test (4, windows-2025, latest)
Windows-2025 runners will change the working directory to a new D:/ drive beginning on 2025-08-18. For more details see https://github.com/actions/runner-images/issues/12744.
test (2, windows-2025, latest)
Windows-2025 runners will change the working directory to a new D:/ drive beginning on 2025-08-18. For more details see https://github.com/actions/runner-images/issues/12744.
test (7, windows-2025, latest)
Windows-2025 runners will change the working directory to a new D:/ drive beginning on 2025-08-18. For more details see https://github.com/actions/runner-images/issues/12744.
test (7, windows-2025, canary)
Windows-2025 runners will change the working directory to a new D:/ drive beginning on 2025-08-18. For more details see https://github.com/actions/runner-images/issues/12744.
test (5, windows-2025, canary)
Windows-2025 runners will change the working directory to a new D:/ drive beginning on 2025-08-18. For more details see https://github.com/actions/runner-images/issues/12744.
test (4, windows-2025, canary)
Windows-2025 runners will change the working directory to a new D:/ drive beginning on 2025-08-18. For more details see https://github.com/actions/runner-images/issues/12744.
test (8, windows-2025, canary)
Windows-2025 runners will change the working directory to a new D:/ drive beginning on 2025-08-18. For more details see https://github.com/actions/runner-images/issues/12744.
test (6, windows-2025, latest)
Windows-2025 runners will change the working directory to a new D:/ drive beginning on 2025-08-18. For more details see https://github.com/actions/runner-images/issues/12744.
test (6, windows-2025, canary)
Windows-2025 runners will change the working directory to a new D:/ drive beginning on 2025-08-18. For more details see https://github.com/actions/runner-images/issues/12744.

Artifacts

Produced during runtime
Name Size Digest
blob-report-canary-1 Expired
120 KB
sha256:0c7c646d402b9bec771744c8e6ecf4db6f13e72a1cd8af13634f9e5f313c8a93
blob-report-canary-2 Expired
18.7 KB
sha256:f2bd955ce830489205b8aa5c9a3588cd1325c6573f019f337fec008baeaead1d
blob-report-canary-3 Expired
176 KB
sha256:4bbc889ccda34a134348da77fdd09bad30b01c69be336201fdbb6b0e3e30ad54
blob-report-canary-4 Expired
18.7 KB
sha256:d8adb900f3055418d81a06523e56ddb02aa5a1bdeb056122ff0b93e7ddef095a
blob-report-canary-5 Expired
83 KB
sha256:ac5ae1f5c0f3e0fbc6b26765714fefabacb5c3875849846144dbae0ada2718e6
blob-report-latest-1 Expired
118 KB
sha256:70d22e6922ab45c444210047faad12e1a1408031e1bf64973dd0bd4ab33adbbe
blob-report-latest-2 Expired
18.7 KB
sha256:bfd3b3cf23bb54b209f918cdf056f48d66cc782d824508a67c1be35364bc7848
blob-report-latest-3 Expired
175 KB
sha256:a1a1fd18388d6c52eea54d42b8829e32cf8e518b0a535996bd45e1c7054edea5
blob-report-latest-4 Expired
18.7 KB
sha256:d6d8fab4ee984b5bac101e4275ec67d67968cd8e74ea9e88cc21f102c389df95
blob-report-latest-5 Expired
63.8 KB
sha256:21b1050569864c62a06a466c65235221c13af4e2c5c872d162d0a5a1f9bc2264
html-report-canary-attempt-1 Expired
740 KB
sha256:39a868a985779d7e1b8141eaa18d6d659d7279009cd037f0c3082368a8651132
html-report-latest-attempt-1 Expired
331 KB
sha256:455d7e4b7989e098da466c0df15222d16ff286c92fc23001e49cf36fbb40e263