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.

Sign up for GitHub

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

Jump to bottom

CI: JUnit upload failure in kind workflow: artifact with this name already exists on the workflow run #2222

Closed
tklauser opened this issue Jan 10, 2024 · 1 comment · Fixed by #2226
Closed

CI: JUnit upload failure in kind workflow: artifact with this name already exists on the workflow run #2222

tklauser opened this issue Jan 10, 2024 · 1 comment · Fixed by #2226
Labels
area/CI Continuous Integration testing issue or flake ci/flake Issues tracking failing (integration or unit) tests.

Comments

@tklauser
Copy link
Member 

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

Seen on https://github.com/cilium/cilium-cli/actions/runs/7469244368/job/20326056243?pr=2221
@tklauser tklauser added area/CI Continuous Integration testing issue or flake ci/flake Issues tracking failing (integration or unit) tests. labels Jan 10, 2024
@tklauser tklauser mentioned this issue Jan 10, 2024
Merged
1 task
@tklauser
Copy link
Member Author

Another occurence on #2224: https://github.com/cilium/cilium-cli/actions/runs/7473789182/job/20338628475?pr=2224

@tklauser tklauser mentioned this issue Jan 10, 2024
Merged
tklauser added a commit that referenced this issue Jan 10, 2024
@tklauser
ci: unique artifact name for junit reports in kind workflow
0b1b621 
Due to some recent changes on GitHub's side, uploading the JUnit reports
on the second job to finish in the kind workflow will fail with:

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

Avoid this from happing by giving the artifacts unique names.

Fixes #2222

Signed-off-by: Tobias Klauser <[email protected]>
@tklauser tklauser mentioned this issue Jan 10, 2024
Merged
tklauser added a commit that referenced this issue Jan 10, 2024
@tklauser
ci: unique artifact name for junit reports in kind workflow
0373ac9 
Due to some recent changes on GitHub's side, uploading the JUnit reports
on the second job to finish in the kind workflow will fail with:

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

Avoid this from happing by giving the artifacts unique names.

Fixes #2222

Signed-off-by: Tobias Klauser <[email protected]>
@thorn3r thorn3r mentioned this issue Jan 30, 2024
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
area/CI Continuous Integration testing issue or flake ci/flake Issues tracking failing (integration or unit) tests.
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

ci: unique artifact name for junit reports in kind workflow cilium/cilium-cli
1 participant
@tklauser