Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[BUG] Kernel unit tests "Failed to CreateArtifact" with 409 Conflict on GitHub Actions #1274

Closed
mryall-mawson opened this issue Sep 28, 2024 · 2 comments
Labels
bug Something isn't working

Comments

@mryall-mawson
Copy link
Contributor

Describe the bug
The kernel unit tests are failing on GitHub Actions (example, another example) with the following error:

Failed to CreateArtifact: Received non-retryable error: Failed request: (409) Conflict: an artifact with this name already exists on the workflow run

This occurs in the "Archive code coverage data" step, with the settings:

with:
    name: coverage-data
    path: FreeRTOS/Test/CMock/build/cmock_test*

Investigation
Looking at the GitHub Actions config, commit 9245b4a was made two weeks ago, which upgraded upload-artifact task from v2 to v4.

There was a published breaking change in upload-artifact v4:

Due to how Artifacts are created in this new version, it is no longer possible to upload to the same named Artifact multiple times. You must either split the uploads into multiple Artifacts with different names, or only upload once. Otherwise you will encounter an error.

This affects the coverage artifacts in the unit test action config, which use the same artifact name across jobs.

(Personally I think this should be fixed in the GH side, but it looks like the GH Actions devs are declining requests to restore the previous functionality. 😞)

To Reproduce

Additional context
I'll open a PR shortly to deduplicate the artifact names in the kernel unit tests action config.

@mryall-mawson mryall-mawson added the bug Something isn't working label Sep 28, 2024
mryall-mawson added a commit to mryall-mawson/FreeRTOS that referenced this issue Sep 28, 2024
@mryall-mawson
Copy link
Contributor Author

PR is open: #1275

@aggarg
Copy link
Member

aggarg commented Sep 30, 2024

Thank you for doing the detailed investigation and fixing the issue.

@aggarg aggarg closed this as completed Sep 30, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants