Skip to content
Run e2e Tests

Run e2e Tests #539

Sign in to view logs

Run e2e Tests

Run e2e Tests #539

Manually triggered November 4, 2024 17:46
@dreamorosidreamorosi
⁠ 941a1d6
chore/tracer_vitest
Status Success
Total duration 4m 44s
Artifacts –

run-e2e-tests.yml

on: workflow_dispatch
Matrix: run-e2e-tests-on-utils
Fit to window
Zoom out
Zoom in

Annotations

48 errors
run-e2e-tests-on-utils (packages/idempotency, 20, arm64)
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Consider adding an extension to the import path.
run-e2e-tests-on-utils (packages/idempotency, 20, arm64)
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Consider adding an extension to the import path.
run-e2e-tests-on-utils (packages/tracer, 18, arm64)
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Consider adding an extension to the import path.
run-e2e-tests-on-utils (packages/tracer, 18, arm64)
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Consider adding an extension to the import path.
run-e2e-tests-on-utils (packages/metrics, 20, x86_64)
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Consider adding an extension to the import path.
run-e2e-tests-on-utils (packages/metrics, 20, x86_64)
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Consider adding an extension to the import path.
run-e2e-tests-on-utils (packages/metrics, 18, x86_64)
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Consider adding an extension to the import path.
run-e2e-tests-on-utils (packages/metrics, 18, x86_64)
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Consider adding an extension to the import path.
run-e2e-tests-on-utils (packages/idempotency, 20, x86_64)
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Consider adding an extension to the import path.
run-e2e-tests-on-utils (packages/idempotency, 20, x86_64)
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Consider adding an extension to the import path.
run-e2e-tests-on-utils (packages/tracer, 20, x86_64)
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Consider adding an extension to the import path.
run-e2e-tests-on-utils (packages/tracer, 20, x86_64)
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Consider adding an extension to the import path.
run-e2e-tests-on-utils (packages/metrics, 20, arm64)
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Consider adding an extension to the import path.
run-e2e-tests-on-utils (packages/metrics, 20, arm64)
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Consider adding an extension to the import path.
run-e2e-tests-on-utils (packages/tracer, 20, arm64)
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Consider adding an extension to the import path.
run-e2e-tests-on-utils (packages/tracer, 20, arm64)
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Consider adding an extension to the import path.
run-e2e-tests-on-utils (packages/metrics, 18, arm64)
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Consider adding an extension to the import path.
run-e2e-tests-on-utils (packages/metrics, 18, arm64)
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Consider adding an extension to the import path.
run-e2e-tests-on-utils (packages/tracer, 18, x86_64)
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Consider adding an extension to the import path.
run-e2e-tests-on-utils (packages/tracer, 18, x86_64)
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Consider adding an extension to the import path.
run-e2e-tests-on-utils (layers, 18, x86_64)
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Consider adding an extension to the import path.
run-e2e-tests-on-utils (layers, 18, x86_64)
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Consider adding an extension to the import path.
run-e2e-tests-on-utils (packages/idempotency, 18, x86_64)
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Consider adding an extension to the import path.
run-e2e-tests-on-utils (packages/idempotency, 18, x86_64)
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Consider adding an extension to the import path.
run-e2e-tests-on-utils (layers, 20, arm64)
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Consider adding an extension to the import path.
run-e2e-tests-on-utils (layers, 20, arm64)
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Consider adding an extension to the import path.
run-e2e-tests-on-utils (layers, 20, x86_64)
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Consider adding an extension to the import path.
run-e2e-tests-on-utils (layers, 20, x86_64)
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Consider adding an extension to the import path.
run-e2e-tests-on-utils (packages/logger, 20, x86_64)
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Consider adding an extension to the import path.
run-e2e-tests-on-utils (packages/logger, 20, x86_64)
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Consider adding an extension to the import path.
run-e2e-tests-on-utils (packages/logger, 20, arm64)
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Consider adding an extension to the import path.
run-e2e-tests-on-utils (packages/logger, 20, arm64)
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Consider adding an extension to the import path.
run-e2e-tests-on-utils (packages/logger, 18, x86_64)
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Consider adding an extension to the import path.
run-e2e-tests-on-utils (packages/logger, 18, x86_64)
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Consider adding an extension to the import path.
run-e2e-tests-on-utils (packages/logger, 18, arm64)
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Consider adding an extension to the import path.
run-e2e-tests-on-utils (packages/logger, 18, arm64)
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Consider adding an extension to the import path.
run-e2e-tests-on-utils (layers, 18, arm64)
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Consider adding an extension to the import path.
run-e2e-tests-on-utils (layers, 18, arm64)
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Consider adding an extension to the import path.
run-e2e-tests-on-utils (packages/parameters, 20, x86_64)
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Consider adding an extension to the import path.
run-e2e-tests-on-utils (packages/parameters, 20, x86_64)
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Consider adding an extension to the import path.
run-e2e-tests-on-utils (packages/parameters, 20, arm64)
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Consider adding an extension to the import path.
run-e2e-tests-on-utils (packages/parameters, 20, arm64)
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Consider adding an extension to the import path.
run-e2e-tests-on-utils (packages/idempotency, 18, arm64)
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Consider adding an extension to the import path.
run-e2e-tests-on-utils (packages/idempotency, 18, arm64)
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Consider adding an extension to the import path.
run-e2e-tests-on-utils (packages/parameters, 18, x86_64)
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Consider adding an extension to the import path.
run-e2e-tests-on-utils (packages/parameters, 18, x86_64)
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Consider adding an extension to the import path.
run-e2e-tests-on-utils (packages/parameters, 18, arm64)
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Consider adding an extension to the import path.
run-e2e-tests-on-utils (packages/parameters, 18, arm64)
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Consider adding an extension to the import path.