-
Notifications
You must be signed in to change notification settings - Fork 1.4k
Make sure the workspace state is saved after adding/removing artifacts. #8475
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
Make sure the workspace state is saved after adding/removing artifacts. #8475
Conversation
@swift-ci please test |
@swift-ci test self hosted windows |
@swift-ci please test |
@swift-ci please test windows |
@swift-ci please test self hosted windows |
I was wondering about withAsyncThrowing. Is that available in Swift 6.0? Appears to be what the Windows failure is about. |
It's a function in swift-package-manager, in Sources/Basics/Concurrency/ThrowingDefer.swift |
@swift-ci please test windows |
@swift-ci please test self hosted windows |
@swift-ci please test |
@swift-ci please test windows |
@swift-ci test self hosted windows |
@swift-ci test self hosted windows |
@swift-ci test |
@swift-ci please test windows |
@swift-ci please test windows |
The workspace state needs to be saved even if the updateBinaryArtifacts call exits early.
Motivation:
If we delete old artifacts, and then the new versions fail to download, without a save() call the workspace state will not know the artifact is no longer there.
Modifications:
Move the
save()
call to adefer
block so it always gets called.Result:
There should be fewer inconsistencies between workspace state and what is actually on disk.