-
Notifications
You must be signed in to change notification settings - Fork 1.4k
Make ignore-lock a flag #7384
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 ignore-lock a flag #7384
Conversation
This allows users to ignore package locking via `--ignore-lock` instead of `--ignore-lock true`.
@swift-ci test |
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.
Is --ignore-lock true
still allowed? If not, I wonder how many workflows we would break or if there's any way to retain compatibility?
With this change the old form is not allowed. I'm happy to also not make this change actually given that use of the option is highly limited |
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.
Sadly yes/no;
|
@swift-ci test |
@swift-ci test windows |
SwiftPM 6 introduces a lock in the package build directory to avoid concurrent builds/tests. Unfortuntely this behavior is needed by the MMIOFileCheckTests currently. This commit adds a flag to avoid locking the package build directory when building with SwiftPM 6. Additionally, I have an inflight PR to change `--ignore-lock true` to `--ignore-lock` so this commit will require a follow-up fix, after that change in SwiftPM is merged (swiftlang/swift-package-manager#7384).
This allows users to ignore package locking via `--ignore-lock` instead of `--ignore-lock true`.
This allows users to ignore package locking via `--ignore-lock` instead of `--ignore-lock true`.
This allows users to ignore package locking via
--ignore-lock
instead of--ignore-lock true
.