Skip to content
Run e2e Tests

Run e2e Tests #514

Sign in to view logs

Run e2e Tests

Run e2e Tests #514

Re-run triggered September 10, 2024 17:37
@dreamorosidreamorosi
⁠ 6864e53
main
Status Failure
Total duration 5m 12s
Artifacts –
This run and associated checks have been archived and are scheduled for deletion. Learn more about checks retention

run-e2e-tests.yml

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

Annotations

52 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'. Did you mean '../types/SSMProvider.js'?
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'. Did you mean './SSMProvider.js'?
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'. Did you mean '../types/SSMProvider.js'?
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'. Did you mean './SSMProvider.js'?
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'. Did you mean '../types/SSMProvider.js'?
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'. Did you mean './SSMProvider.js'?
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'. Did you mean '../types/SSMProvider.js'?
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'. Did you mean './SSMProvider.js'?
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'. Did you mean '../types/SSMProvider.js'?
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'. Did you mean './SSMProvider.js'?
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'. Did you mean '../types/SSMProvider.js'?
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'. Did you mean './SSMProvider.js'?
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'. Did you mean '../types/SSMProvider.js'?
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'. Did you mean './SSMProvider.js'?
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'. Did you mean '../types/SSMProvider.js'?
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'. Did you mean './SSMProvider.js'?
run-e2e-tests-on-utils (layers, 18, arm64)
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Did you mean '../types/SSMProvider.js'?
run-e2e-tests-on-utils (layers, 18, arm64)
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Did you mean './SSMProvider.js'?
run-e2e-tests-on-utils (layers, 18, arm64)
Process completed with exit code 1.
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'. Did you mean '../types/SSMProvider.js'?
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'. Did you mean './SSMProvider.js'?
run-e2e-tests-on-utils (layers, 20, arm64)
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Did you mean '../types/SSMProvider.js'?
run-e2e-tests-on-utils (layers, 20, arm64)
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Did you mean './SSMProvider.js'?
run-e2e-tests-on-utils (layers, 20, arm64)
Process completed with exit code 1.
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'. Did you mean '../types/SSMProvider.js'?
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'. Did you mean './SSMProvider.js'?
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'. Did you mean '../types/SSMProvider.js'?
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'. Did you mean './SSMProvider.js'?
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'. Did you mean '../types/SSMProvider.js'?
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'. Did you mean './SSMProvider.js'?
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'. Did you mean '../types/SSMProvider.js'?
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'. Did you mean './SSMProvider.js'?
run-e2e-tests-on-utils (layers, 20, x86_64)
Process completed with exit code 1.
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'. Did you mean '../types/SSMProvider.js'?
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'. Did you mean './SSMProvider.js'?
run-e2e-tests-on-utils (layers, 18, x86_64)
Process completed with exit code 1.
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'. Did you mean '../types/SSMProvider.js'?
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'. Did you mean './SSMProvider.js'?
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'. Did you mean '../types/SSMProvider.js'?
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'. Did you mean './SSMProvider.js'?
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'. Did you mean '../types/SSMProvider.js'?
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'. Did you mean './SSMProvider.js'?
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'. Did you mean '../types/SSMProvider.js'?
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'. Did you mean './SSMProvider.js'?
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'. Did you mean '../types/SSMProvider.js'?
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'. Did you mean './SSMProvider.js'?
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'. Did you mean '../types/SSMProvider.js'?
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'. Did you mean './SSMProvider.js'?
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'. Did you mean '../types/SSMProvider.js'?
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'. Did you mean './SSMProvider.js'?
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'. Did you mean '../types/SSMProvider.js'?
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'. Did you mean './SSMProvider.js'?