CI: Build & Test #401
Triggered via schedule
April 6, 2026 00:30
Zen-cronic
Status
Cancelled
Total duration
1d 0h 8m 27s
Artifacts
24
build.yml
on: schedule
Get Metadata
6s
Check PR branches
0s
Matrix: job_browser_loader_tests
Matrix: job_browser_playwright_tests
Matrix: job_node_core_integration_tests
Matrix: job_node_integration_tests
Matrix: job_node_unit_tests
Matrix: job_remix_integration_tests
Size Check
1m 52s
Lint
56s
Circular Dependency Check
1m 18s
Upload Artifacts
0s
Browser Unit Tests
4m 4s
Bun Unit Tests
35s
Deno Unit Tests
47s
Cloudflare Integration Tests
55s
Node Overhead Check
3m 32s
Check for faulty .d.ts files
30s
Matrix: job_e2e_tests
Matrix: job_optional_e2e_tests
All required jobs passed or were skipped
2s
Annotations
43 errors and 121 warnings
|
Node (24) Unit Tests
Failed to parse /home/runner/work/sentry-javascript/sentry-javascript/packages/sveltekit/vitest.junit.xml: Entity expansion limit exceeded: 1002 > 1000
|
|
Node (24) Unit Tests
Failed to parse /home/runner/work/sentry-javascript/sentry-javascript/packages/node-core/vitest.junit.xml: Entity expansion limit exceeded: 1002 > 1000
|
|
Node (24) Unit Tests
Failed to parse /home/runner/work/sentry-javascript/sentry-javascript/packages/node/vitest.junit.xml: Entity expansion limit exceeded: 1001 > 1000
|
|
Node (24) Unit Tests
Failed to parse /home/runner/work/sentry-javascript/sentry-javascript/packages/nextjs/vitest.junit.xml: Entity expansion limit exceeded: 1002 > 1000
|
|
Node (24) Unit Tests
Failed to parse /home/runner/work/sentry-javascript/sentry-javascript/packages/core/vitest.junit.xml: Entity expansion limit exceeded: 1002 > 1000
|
|
Node (20) Unit Tests
Failed to parse /home/runner/work/sentry-javascript/sentry-javascript/packages/sveltekit/vitest.junit.xml: Entity expansion limit exceeded: 1002 > 1000
|
|
Node (20) Unit Tests
Failed to parse /home/runner/work/sentry-javascript/sentry-javascript/packages/node-core/vitest.junit.xml: Entity expansion limit exceeded: 1002 > 1000
|
|
Node (20) Unit Tests
Failed to parse /home/runner/work/sentry-javascript/sentry-javascript/packages/node/vitest.junit.xml: Entity expansion limit exceeded: 1001 > 1000
|
|
Node (20) Unit Tests
Failed to parse /home/runner/work/sentry-javascript/sentry-javascript/packages/nextjs/vitest.junit.xml: Entity expansion limit exceeded: 1002 > 1000
|
|
Node (20) Unit Tests
Failed to parse /home/runner/work/sentry-javascript/sentry-javascript/packages/core/vitest.junit.xml: Entity expansion limit exceeded: 1002 > 1000
|
|
Node (18) Unit Tests
Failed to parse /home/runner/work/sentry-javascript/sentry-javascript/packages/sveltekit/vitest.junit.xml: Entity expansion limit exceeded: 1002 > 1000
|
|
Node (18) Unit Tests
Failed to parse /home/runner/work/sentry-javascript/sentry-javascript/packages/node-core/vitest.junit.xml: Entity expansion limit exceeded: 1002 > 1000
|
|
Node (18) Unit Tests
Failed to parse /home/runner/work/sentry-javascript/sentry-javascript/packages/node/vitest.junit.xml: Entity expansion limit exceeded: 1001 > 1000
|
|
Node (18) Unit Tests
Failed to parse /home/runner/work/sentry-javascript/sentry-javascript/packages/nextjs/vitest.junit.xml: Entity expansion limit exceeded: 1002 > 1000
|
|
Node (18) Unit Tests
Failed to parse /home/runner/work/sentry-javascript/sentry-javascript/packages/core/vitest.junit.xml: Entity expansion limit exceeded: 1002 > 1000
|
|
Browser Unit Tests
Failed to parse /home/runner/work/sentry-javascript/sentry-javascript/packages/replay-internal/vitest.junit.xml: Entity expansion limit exceeded: 1001 > 1000
|
|
Browser Unit Tests
Failed to parse /home/runner/work/sentry-javascript/sentry-javascript/packages/react/vitest.junit.xml: Entity expansion limit exceeded: 1002 > 1000
|
|
Browser Unit Tests
Failed to parse /home/runner/work/sentry-javascript/sentry-javascript/packages/browser/vitest.junit.xml: Entity expansion limit exceeded: 1001 > 1000
|
|
Node (22) Unit Tests
Failed to parse /home/runner/work/sentry-javascript/sentry-javascript/packages/sveltekit/vitest.junit.xml: Entity expansion limit exceeded: 1002 > 1000
|
|
Node (22) Unit Tests
Failed to parse /home/runner/work/sentry-javascript/sentry-javascript/packages/node-core/vitest.junit.xml: Entity expansion limit exceeded: 1002 > 1000
|
|
Node (22) Unit Tests
Failed to parse /home/runner/work/sentry-javascript/sentry-javascript/packages/node/vitest.junit.xml: Entity expansion limit exceeded: 1001 > 1000
|
|
Node (22) Unit Tests
Failed to parse /home/runner/work/sentry-javascript/sentry-javascript/packages/nextjs/vitest.junit.xml: Entity expansion limit exceeded: 1002 > 1000
|
|
Node (22) Unit Tests
Failed to parse /home/runner/work/sentry-javascript/sentry-javascript/packages/core/vitest.junit.xml: Entity expansion limit exceeded: 1002 > 1000
|
|
Prepare E2E tests
The job has exceeded the maximum execution time while awaiting a runner for 24h0m0s
|
|
Playwright bundle_logs_metrics Tests
The job has exceeded the maximum execution time while awaiting a runner for 24h0m0s
|
|
Playwright bundle_tracing Tests
The job has exceeded the maximum execution time while awaiting a runner for 24h0m0s
|
|
Playwright esm (3/4) Tests
The job has exceeded the maximum execution time while awaiting a runner for 24h0m0s
|
|
Playwright bundle_replay Tests
The job has exceeded the maximum execution time while awaiting a runner for 24h0m0s
|
|
Playwright bundle_tracing_replay_feedback_logs_metrics_min firefox Tests
The job has exceeded the maximum execution time while awaiting a runner for 24h0m0s
|
|
Playwright bundle_replay_logs_metrics Tests
The job has exceeded the maximum execution time while awaiting a runner for 24h0m0s
|
|
Playwright esm (2/4) Tests
The job has exceeded the maximum execution time while awaiting a runner for 24h0m0s
|
|
Playwright bundle_tracing_replay_logs_metrics Tests
The job has exceeded the maximum execution time while awaiting a runner for 24h0m0s
|
|
Playwright bundle_tracing_replay_feedback_logs_metrics Tests
The job has exceeded the maximum execution time while awaiting a runner for 24h0m0s
|
|
Playwright bundle_tracing_replay_feedback_logs_metrics_min Tests
The job has exceeded the maximum execution time while awaiting a runner for 24h0m0s
|
|
Playwright esm (1/4) Tests
The job has exceeded the maximum execution time while awaiting a runner for 24h0m0s
|
|
Playwright bundle_tracing_logs_metrics Tests
The job has exceeded the maximum execution time while awaiting a runner for 24h0m0s
|
|
Playwright bundle_tracing_replay_feedback Tests
The job has exceeded the maximum execution time while awaiting a runner for 24h0m0s
|
|
Playwright esm (4/4) Tests
The job has exceeded the maximum execution time while awaiting a runner for 24h0m0s
|
|
Playwright bundle_tracing_replay_feedback_logs_metrics_min webkit Tests
The job has exceeded the maximum execution time while awaiting a runner for 24h0m0s
|
|
Playwright bundle_min Tests
The job has exceeded the maximum execution time while awaiting a runner for 24h0m0s
|
|
Playwright bundle_tracing_replay Tests
The job has exceeded the maximum execution time while awaiting a runner for 24h0m0s
|
|
Playwright bundle Tests
The job has exceeded the maximum execution time while awaiting a runner for 24h0m0s
|
|
All required jobs passed or were skipped
Process completed with exit code 1.
|
|
Get Metadata
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: dorny/paths-filter@v3.0.1, mydea/pr-labels-action@fn/bump-node20. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Get Metadata
Ref develop is not checked out - results might be incorrect!
|
|
Get Metadata
'before' field is missing in event payload - changes will be detected from last commit
|
|
Check file formatting
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Build
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Check for faulty .d.ts files
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@v4, actions/download-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Bun Unit Tests
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@v4, actions/download-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Cloudflare Integration Tests
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@v4, actions/download-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Lint
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@v4, actions/download-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
typescript-eslint(no-base-to-string):
packages/core/src/tracing/google-genai/streaming.ts#L50
'message' will use Object's default stringification format ('[object Object]') when stringified.
|
|
typescript-eslint(no-base-to-string):
packages/core/src/tracing/google-genai/streaming.ts#L49
'message' will use Object's default stringification format ('[object Object]') when stringified.
|
|
typescript-eslint(no-base-to-string):
packages/core/src/integrations/mcp-server/attributeExtraction.ts#L85
'params.uri' will use Object's default stringification format ('[object Object]') when stringified.
|
|
typescript-eslint(no-base-to-string):
packages/core/src/integrations/mcp-server/attributeExtraction.ts#L84
'params.uri' will use Object's default stringification format ('[object Object]') when stringified.
|
|
typescript-eslint(no-base-to-string):
packages/core/src/integrations/mcp-server/attributeExtraction.ts#L78
'params.message' will use Object's default stringification format ('[object Object]') when stringified.
|
|
typescript-eslint(no-base-to-string):
packages/core/src/integrations/mcp-server/attributeExtraction.ts#L66
'params.progressToken' will use Object's default stringification format ('[object Object]') when stringified.
|
|
typescript-eslint(no-base-to-string):
packages/core/src/integrations/mcp-server/attributeExtraction.ts#L54
'params.logger' will use Object's default stringification format ('[object Object]') when stringified.
|
|
typescript-eslint(no-base-to-string):
packages/core/src/integrations/mcp-server/attributeExtraction.ts#L51
'params.level' will use Object's default stringification format ('[object Object]') when stringified.
|
|
typescript-eslint(no-base-to-string):
packages/core/src/integrations/mcp-server/attributeExtraction.ts#L45
'params.reason' will use Object's default stringification format ('[object Object]') when stringified.
|
|
typescript-eslint(no-base-to-string):
packages/core/src/integrations/mcp-server/attributeExtraction.ts#L42
'params.requestId' will use Object's default stringification format ('[object Object]') when stringified.
|
|
Circular Dependency Check
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@v4, actions/download-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
PW loader_debug Tests
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@v4, actions/download-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
PW loader_debug Tests
Supported formats: clover, cobertura, jacoco, lcov, istanbul, go, codecov
|
|
PW loader_debug Tests
No coverage files found
|
|
PW loader_tracing Tests
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@v4, actions/download-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
PW loader_tracing Tests
Supported formats: clover, cobertura, jacoco, lcov, istanbul, go, codecov
|
|
PW loader_tracing Tests
No coverage files found
|
|
Deno Unit Tests
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@v4, actions/download-artifact@v4, denoland/setup-deno@v2.0.3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Size Check
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ./dev-packages/size-limit-gh-action, actions/cache/restore@v4, actions/download-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Remix (Node 20) Tests
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@v4, actions/download-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Remix (Node 20) Tests
Supported formats: clover, cobertura, jacoco, lcov, istanbul, go, codecov
|
|
Remix (Node 20) Tests
No coverage files found
|
|
Remix (Node 22) Tests
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@v4, actions/download-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Remix (Node 22) Tests
Supported formats: clover, cobertura, jacoco, lcov, istanbul, go, codecov
|
|
Remix (Node 22) Tests
No coverage files found
|
|
Node (18) Node-Core Integration Tests
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@v4, actions/download-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Node (18) Node-Core Integration Tests
Supported formats: clover, cobertura, jacoco, lcov, istanbul, go, codecov
|
|
Node (18) Node-Core Integration Tests
No coverage files found
|
|
Node (18) Node-Core Integration Tests
Please ensure your test framework is generating JUnit XML output.
|
|
Node (18) Node-Core Integration Tests
No JUnit XML files found matching pattern: dev-packages/node-core-integration-tests/**/*.junit.xml
|
|
Node (18) Node-Core Integration Tests
No files found matching pattern: dev-packages/node-core-integration-tests/**/*.junit.xml
|
|
Remix (Node 18) Tests
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@v4, actions/download-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Remix (Node 18) Tests
Supported formats: clover, cobertura, jacoco, lcov, istanbul, go, codecov
|
|
Remix (Node 18) Tests
No coverage files found
|
|
Node (24) Node-Core Integration Tests
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@v4, actions/download-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Node (24) Node-Core Integration Tests
Supported formats: clover, cobertura, jacoco, lcov, istanbul, go, codecov
|
|
Node (24) Node-Core Integration Tests
No coverage files found
|
|
Node (24) Node-Core Integration Tests
Please ensure your test framework is generating JUnit XML output.
|
|
Node (24) Node-Core Integration Tests
No JUnit XML files found matching pattern: dev-packages/node-core-integration-tests/**/*.junit.xml
|
|
Node (24) Node-Core Integration Tests
No files found matching pattern: dev-packages/node-core-integration-tests/**/*.junit.xml
|
|
PW loader_replay Tests
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@v4, actions/download-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
PW loader_replay Tests
Supported formats: clover, cobertura, jacoco, lcov, istanbul, go, codecov
|
|
PW loader_replay Tests
No coverage files found
|
|
Node (20) Node-Core Integration Tests
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@v4, actions/download-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Node (20) Node-Core Integration Tests
Supported formats: clover, cobertura, jacoco, lcov, istanbul, go, codecov
|
|
Node (20) Node-Core Integration Tests
No coverage files found
|
|
Node (20) Node-Core Integration Tests
Please ensure your test framework is generating JUnit XML output.
|
|
Node (20) Node-Core Integration Tests
No JUnit XML files found matching pattern: dev-packages/node-core-integration-tests/**/*.junit.xml
|
|
Node (20) Node-Core Integration Tests
No files found matching pattern: dev-packages/node-core-integration-tests/**/*.junit.xml
|
|
Remix (Node 24) Tests
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@v4, actions/download-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Remix (Node 24) Tests
Supported formats: clover, cobertura, jacoco, lcov, istanbul, go, codecov
|
|
Remix (Node 24) Tests
No coverage files found
|
|
PW loader_replay_buffer Tests
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@v4, actions/download-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
PW loader_replay_buffer Tests
Supported formats: clover, cobertura, jacoco, lcov, istanbul, go, codecov
|
|
PW loader_replay_buffer Tests
No coverage files found
|
|
PW loader_tracing_replay Tests
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@v4, actions/download-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
PW loader_tracing_replay Tests
Supported formats: clover, cobertura, jacoco, lcov, istanbul, go, codecov
|
|
PW loader_tracing_replay Tests
No coverage files found
|
|
PW loader_base Tests
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@v4, actions/download-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
PW loader_base Tests
Supported formats: clover, cobertura, jacoco, lcov, istanbul, go, codecov
|
|
PW loader_base Tests
No coverage files found
|
|
Node Overhead Check
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@v4, actions/download-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Node (24) Unit Tests
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@v4, actions/download-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
PW loader_eager Tests
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@v4, actions/download-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
PW loader_eager Tests
Supported formats: clover, cobertura, jacoco, lcov, istanbul, go, codecov
|
|
PW loader_eager Tests
No coverage files found
|
|
Node (20) Unit Tests
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@v4, actions/download-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Node (18) Unit Tests
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@v4, actions/download-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Node (22) Node-Core Integration Tests
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@v4, actions/download-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Node (22) Node-Core Integration Tests
Supported formats: clover, cobertura, jacoco, lcov, istanbul, go, codecov
|
|
Node (22) Node-Core Integration Tests
No coverage files found
|
|
Node (22) Node-Core Integration Tests
Please ensure your test framework is generating JUnit XML output.
|
|
Node (22) Node-Core Integration Tests
No JUnit XML files found matching pattern: dev-packages/node-core-integration-tests/**/*.junit.xml
|
|
Node (22) Node-Core Integration Tests
No files found matching pattern: dev-packages/node-core-integration-tests/**/*.junit.xml
|
|
Browser Unit Tests
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@v4, actions/download-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Node (24) (TS 3.8) Node-Core Integration Tests
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@v4, actions/download-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Node (24) (TS 3.8) Node-Core Integration Tests
Supported formats: clover, cobertura, jacoco, lcov, istanbul, go, codecov
|
|
Node (24) (TS 3.8) Node-Core Integration Tests
No coverage files found
|
|
Node (24) (TS 3.8) Node-Core Integration Tests
Please ensure your test framework is generating JUnit XML output.
|
|
Node (24) (TS 3.8) Node-Core Integration Tests
No JUnit XML files found matching pattern: dev-packages/node-core-integration-tests/**/*.junit.xml
|
|
Node (24) (TS 3.8) Node-Core Integration Tests
No files found matching pattern: dev-packages/node-core-integration-tests/**/*.junit.xml
|
|
Node (22) Unit Tests
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@v4, actions/download-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Node (20) Integration Tests
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@v4, actions/download-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Node (20) Integration Tests
Supported formats: clover, cobertura, jacoco, lcov, istanbul, go, codecov
|
|
Node (20) Integration Tests
No coverage files found
|
|
Node (20) Integration Tests
Please ensure your test framework is generating JUnit XML output.
|
|
Node (20) Integration Tests
No JUnit XML files found matching pattern: dev-packages/node-integration-tests/**/*.junit.xml
|
|
Node (20) Integration Tests
No files found matching pattern: dev-packages/node-integration-tests/**/*.junit.xml
|
|
Node (24) Integration Tests
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@v4, actions/download-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Node (24) Integration Tests
Supported formats: clover, cobertura, jacoco, lcov, istanbul, go, codecov
|
|
Node (24) Integration Tests
No coverage files found
|
|
Node (24) Integration Tests
Please ensure your test framework is generating JUnit XML output.
|
|
Node (24) Integration Tests
No JUnit XML files found matching pattern: dev-packages/node-integration-tests/**/*.junit.xml
|
|
Node (24) Integration Tests
No files found matching pattern: dev-packages/node-integration-tests/**/*.junit.xml
|
|
Node (24) (TS 3.8) Integration Tests
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@v4, actions/download-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Node (24) (TS 3.8) Integration Tests
Supported formats: clover, cobertura, jacoco, lcov, istanbul, go, codecov
|
|
Node (24) (TS 3.8) Integration Tests
No coverage files found
|
|
Node (24) (TS 3.8) Integration Tests
Please ensure your test framework is generating JUnit XML output.
|
|
Node (24) (TS 3.8) Integration Tests
No JUnit XML files found matching pattern: dev-packages/node-integration-tests/**/*.junit.xml
|
|
Node (24) (TS 3.8) Integration Tests
No files found matching pattern: dev-packages/node-integration-tests/**/*.junit.xml
|
|
Node (18) Integration Tests
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@v4, actions/download-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Node (18) Integration Tests
Supported formats: clover, cobertura, jacoco, lcov, istanbul, go, codecov
|
|
Node (18) Integration Tests
No coverage files found
|
|
Node (18) Integration Tests
Please ensure your test framework is generating JUnit XML output.
|
|
Node (18) Integration Tests
No JUnit XML files found matching pattern: dev-packages/node-integration-tests/**/*.junit.xml
|
|
Node (18) Integration Tests
No files found matching pattern: dev-packages/node-integration-tests/**/*.junit.xml
|
|
Node (22) Integration Tests
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@v4, actions/download-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Node (22) Integration Tests
Supported formats: clover, cobertura, jacoco, lcov, istanbul, go, codecov
|
|
Node (22) Integration Tests
No coverage files found
|
|
Node (22) Integration Tests
Please ensure your test framework is generating JUnit XML output.
|
|
Node (22) Integration Tests
No JUnit XML files found matching pattern: dev-packages/node-integration-tests/**/*.junit.xml
|
|
Node (22) Integration Tests
No files found matching pattern: dev-packages/node-integration-tests/**/*.junit.xml
|
Artifacts
Produced during runtime
| Name | Size | Digest | |
|---|---|---|---|
|
build-output
Expired
|
32.2 MB |
sha256:44123078d76eb3d501e202e6d6988d66b13802e83a7668792d549e5a4f69942c
|
|
|
codecov-coverage-results-develop-job_browser_unit_tests
|
92.6 KB |
sha256:2be30b4ab9752941ac9d643add4bd3140957a0464a96ff943f40f7b3ea4996cc
|
|
|
codecov-coverage-results-develop-job_node_unit_tests-18
|
225 KB |
sha256:32475dd8f4ed803ee623714de8886d28ec9420f4b9867f6f4f846708289d22d1
|
|
|
codecov-coverage-results-develop-job_node_unit_tests-20
|
233 KB |
sha256:e3d9f3726564583813e4302e13a06e6b055ac2f2029dac9cec679ce85473029c
|
|
|
codecov-coverage-results-develop-job_node_unit_tests-22
|
233 KB |
sha256:f321bea19263a27ea03d3cf17fc7b0808f0ec98f956cfadcf5ef46174a00af8f
|
|
|
codecov-coverage-results-develop-job_node_unit_tests-24
|
233 KB |
sha256:04e51f2921cb05051038876bb96dfe4cc246be730a3b81aa9a0e941a9f24d1a0
|
|
|
codecov-test-results-develop-job_browser_loader_tests-browser-loader-loader_base
|
240 Bytes |
sha256:c2f498ec0bb8206122c839e7841c081c1ee7b677f6a4f24a9525ba90a18c0c66
|
|
|
codecov-test-results-develop-job_browser_loader_tests-browser-loader-loader_debug
|
240 Bytes |
sha256:b50537a667fe803b8f012115da81c2dcbf13a9353bc7ff94a7c18fe9319f7676
|
|
|
codecov-test-results-develop-job_browser_loader_tests-browser-loader-loader_eager
|
240 Bytes |
sha256:70689e48f78a6f23643b781cd8decfed13c34a1cbf31852782ec01c5dc3abdc7
|
|
|
codecov-test-results-develop-job_browser_loader_tests-browser-loader-loader_replay
|
240 Bytes |
sha256:8504e9daa350003e5740e40937de0f41bea35d75e272340bf60050219c26a4c6
|
|
|
codecov-test-results-develop-job_browser_loader_tests-browser-loader-loader_replay_buffer
|
237 Bytes |
sha256:f3b465e73eda1f5cfa4e3fba1fb8bd2fda6897d8730b658fa625737b3cd64b40
|
|
|
codecov-test-results-develop-job_browser_loader_tests-browser-loader-loader_tracing
|
243 Bytes |
sha256:2e78d4df5e5d90047a0b5beff43e78b2ab3ba9f9315a6874b7651f6369227971
|
|
|
codecov-test-results-develop-job_browser_loader_tests-browser-loader-loader_tracing_replay
|
238 Bytes |
sha256:91f3722c0ddeb28eab1aa9e953d0e07c6ca6c66e4547555e06464258d69fd486
|
|
|
codecov-test-results-develop-job_browser_unit_tests
|
242 Bytes |
sha256:209757c0c2f7c4b376090013b96ced8a570c569a1c0cf684d8de180cc3a6c1bc
|
|
|
codecov-test-results-develop-job_node_unit_tests-18
|
249 Bytes |
sha256:682fb2939902c834410c4a40cf6681a08ac3a06b41044c5e4edeea883730f1cd
|
|
|
codecov-test-results-develop-job_node_unit_tests-20
|
246 Bytes |
sha256:5dee659d7ba62dd2867e63ac0867ef0a19062ebfed9da3be8c149900a0dcec01
|
|
|
codecov-test-results-develop-job_node_unit_tests-22
|
247 Bytes |
sha256:4e6414762f51af5b468b3161ba4eededccb10b2b188fabf56a4ae52f270c593f
|
|
|
codecov-test-results-develop-job_node_unit_tests-24
|
247 Bytes |
sha256:e392ea4e89bcd61f7ed9b52d1b50961469c6b31a9800c5b5b2e17296f0ef19c7
|
|
|
codecov-test-results-develop-job_remix_integration_tests-18
|
235 Bytes |
sha256:30f7fe97a15ce390552b18f1962ce60f00fac39d09cbc7f250c213632d71cb63
|
|
|
codecov-test-results-develop-job_remix_integration_tests-20
|
235 Bytes |
sha256:b4dc47d9e90a4057792a831a1f427cd3306a7a6cb20d3d68744ab4246dab3d34
|
|
|
codecov-test-results-develop-job_remix_integration_tests-22
|
235 Bytes |
sha256:3b1f16535660cd7c15de1eea81bd9081991eec8ae79206dfc1e5eaf8089f654c
|
|
|
codecov-test-results-develop-job_remix_integration_tests-24
|
231 Bytes |
sha256:f6d0069c58cc5f01534989b7120d239109eb01665cdfb0b35c449c21fe57b719
|
|
|
node-overhead-action
|
282 Bytes |
sha256:a8e7afa6f43d9c6b5f4d89f247d592a059fed1a83005ce0420ae3224d5ed64ab
|
|
|
size-limit-action
|
1021 Bytes |
sha256:9e6062c8aa8c3b22d1f36f8d9b000753a61f549dd6f19b79fa752255767d79ef
|
|