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

Upload-artifact error in edx-platform unit tests CI #34985

Closed
timmc-edx opened this issue Jun 13, 2024 · 1 comment · Fixed by #35034
Closed

Upload-artifact error in edx-platform unit tests CI #34985

timmc-edx opened this issue Jun 13, 2024 · 1 comment · Fixed by #35034
Assignees

Comments

@timmc-edx
Copy link
Contributor

timmc-edx commented Jun 13, 2024

Starting 2024-06-12 we've seen a number of instances of an error during unit-test CI runs on the master branch: an artifact with this name already exists on the workflow run. It seems to always succeed on re-run, but is affecting most or all commits as of 2024-06-13.

Notes

Sample instance

Run actions/upload-artifact@v4
With the provided path, there will be 1 file uploaded
Artifact 'pytest-warnings-json' (ID: 1597981853) deleted
Artifact name is valid!
Root directory input is valid!
Error: Failed to CreateArtifact: Received non-retryable error: Failed request: (409) Conflict: an artifact with this name already exists on the workflow run

The config reported for upload-artifact in that run:

   with:
    name: pytest-warnings-json
    path: test_root/log/pytest_warnings*.json
  
    overwrite: true
    if-no-files-found: warn
    compression-level: 6
@timmc-edx timmc-edx self-assigned this Jun 13, 2024
@feanil
Copy link
Contributor

feanil commented Jun 17, 2024

So I took a quick look into this and it gets a bit weirder. It looks like this step downloads the warnings files to compile the full report but there is no step in any of the workflows that uploads the warnings files anymore...so...it looks like it just downloads an old one and generates the same report each time? I might be missing something but if it's causing issues and it's broken, it may make sense to just comment out this job until we can get it fully working again.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Archived in project
Development

Successfully merging a pull request may close this issue.

2 participants