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

Downloading multiple artifacts with the same file name corrupts them. #2774

Closed
colincoghill opened this issue May 8, 2024 · 1 comment · Fixed by #2878
Closed

Downloading multiple artifacts with the same file name corrupts them. #2774

colincoghill opened this issue May 8, 2024 · 1 comment · Fixed by #2878

Comments

@colincoghill
Copy link

We've recently diagnosed a situation where artifacts appeared to be getting corrupted and discovered it's when multiple are created with the same name in different steps, then downloaded to a final step.

eg.

Step 1: Uploads artifacts:

  • package_amd64.deb
  • package_all.deb

Step 2: Uploads artifacts:

  • package_arm64.deb
  • package_all.deb

Step 3: Downloads all artifacts from step 1 and 2:

  • package_amd64.deb
  • package_arm64.deb
  • package_all.deb <- will be corrupted combination of the two.

This took a while to diagnose because the corrupted file is the correct size and because it's a mixing of two similar files (in our case they were supposedly identical but because some file date stamps were different, the compressed content was unusable).

The buildkite agent code that downloads artifacts from S3 appears to grab a list of all artifacts and downloads them in parallel, it looks likely that this is where the problem happens.

I realise creating multiple artifacts with the same name is not recommended, but it's a very easy mistake to make.

Is it possible to either fix this behaviour or at least make it clearer in the documentation that this is an easy to make mistake.

@moskyb
Copy link
Contributor

moskyb commented May 15, 2024

hey @colincoghill! this is definitely not the intended behaviour - i suspect that the two artifacts are being erroneously downloaded into the same place and splinching with each other. i'll raise an escalation internally and try to get this fixed for you.

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

Successfully merging a pull request may close this issue.

2 participants