-
Notifications
You must be signed in to change notification settings - Fork 385
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
[v5.16 Backport] storage: use race-free AddNames
instead of SetNames
#1502
[v5.16 Backport] storage: use race-free AddNames
instead of SetNames
#1502
Conversation
…d126860cd51 Signed-off-by: Aditya R <[email protected]>
Commits from parallel builds using `SetNames` removes `names` from storage for other builds. Use race-free atomic `AddNames` to prevent breaking of parallel builds. Signed-off-by: Aditya R <[email protected]>
Signed-off-by: Aditya R <[email protected]>
Signed-off-by: Aditya R <[email protected]>
Wait for a release from: containers/storage#1173 |
@containers/image-maintainers PTAL. I still have to wait for |
@mtrmac @vrothberg Could you please create a |
Done. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
ACK to the code (but blocked on a c/storage release).
WRT the test failures, is it possible to fix that by updating SKOPEO_BRANCH
on this branch to an appropriate consumer of c/image 5.16?
@mtrmac I am marking this as draft since this PR might not be needed as @TomSweeneyRedHat confirmed that we are only backporting to So marking this PR as draft and will open a replacement on |
Raised a replacement PR here: #1503 |
@flouthoc I'm going to close this for now. However, we may resurrect it if we have to backport later. |
Backport of: #1480
Commits from parallel builds using
SetNames
removesnames
fromstorage for other builds.
Use race-free atomic
AddNames
to prevent breaking of parallel builds.