Skip to content

refactor: streamline error handling in LeadController using MagicAI e… #64

refactor: streamline error handling in LeadController using MagicAI e…

refactor: streamline error handling in LeadController using MagicAI e… #64

Triggered via push March 12, 2025 09:02
Status Failure
Total duration 3m 33s
Artifacts 1
Matrix: admin_playwright_test
Fit to window
Zoom out
Zoom in

Annotations

5 errors and 3 warnings
Admin | Playwright Tests | Shard 5 Of 6
Process completed with exit code 1.
Admin | Playwright Tests | Shard 3 Of 6
Failed to CreateArtifact: Received non-retryable error: Failed request: (409) Conflict: an artifact with this name already exists on the workflow run
Admin | Playwright Tests | Shard 3 Of 6
Process completed with exit code 1.
Admin | Playwright Tests | Shard 2 Of 6
Failed to CreateArtifact: Received non-retryable error: Failed request: (409) Conflict: an artifact with this name already exists on the workflow run
Admin | Playwright Tests | Shard 2 Of 6
Process completed with exit code 1.
Admin | Playwright Tests | Shard 4 Of 6
No files were found with the provided path: packages/Webkul/Admin/tests/e2e-pw/test-results. No artifacts will be uploaded.
Admin | Playwright Tests | Shard 1 Of 6
No files were found with the provided path: packages/Webkul/Admin/tests/e2e-pw/test-results. No artifacts will be uploaded.
Admin | Playwright Tests | Shard 6 Of 6
No files were found with the provided path: packages/Webkul/Admin/tests/e2e-pw/test-results. No artifacts will be uploaded.

Artifacts

Produced during runtime
Name Size Digest
test-results Expired
2.23 MB
sha256:73f225d1b612d2e0c3fb0bea05bbf93b30dcf75b6c9e4bac6b2bd5b5d7d49a7a