Skip to content

Create rules for backwards compatibility with database-specific error codes #199

Create rules for backwards compatibility with database-specific error codes

Create rules for backwards compatibility with database-specific error codes #199

Triggered via pull request December 20, 2024 17:18
Status Failure
Total duration 20m 41s
Artifacts 2

global-ci.yaml

on: pull_request
Build tackle2-hub
2m 58s
Build tackle2-hub
e2e  /  e2e-api-integration-tests
17m 24s
e2e / e2e-api-integration-tests
Matrix: e2e / e2e-ui-integration-tests
Fit to window
Zoom out
Zoom in

Annotations

3 errors and 2 warnings
e2e / e2e-ui-integration-tests (tier0)
Process completed with exit code 2.
e2e / e2e-api-integration-tests
Process completed with exit code 2.
e2e / e2e-api-integration-tests
Failed to CreateArtifact: Received non-retryable error: Failed request: (409) Conflict: an artifact with this name already exists on the workflow run
e2e / e2e-ui-integration-tests (tier0)
No files were found with the provided path: tackle-ui-tests/cypress/reports tackle-ui-tests/cypress/screenshots. No artifacts will be uploaded.
Deprecation notice: v1, v2, and v3 of the artifact actions
The following artifacts were uploaded using a version of actions/upload-artifact that is scheduled for deprecation: "tackle2-hub". Please update your workflow to use v4 of the artifact actions. Learn more: https://github.blog/changelog/2024-04-16-deprecation-notice-v3-of-the-artifact-actions/

Artifacts

Produced during runtime
Name Size
debug-output
5.02 KB
tackle2-hub Expired
181 MB