-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
Fix Operation.swift Operation addDependency bug #2488
Conversation
Everything works fine on the Darwin platform. As the Operation.swift changes so much between swift-5.0 and the current master branch. I guess the Foundation team may have a new design for Operation&OperationQueue and everything is in progress. |
@swift-ci please test and merge |
The new test is segfaulting. |
@millenomi The test case failed as I only fixed the |
@swift-ci please test |
@millenomi I updated the test case to only handle the |
The other test uncovered a separate bug that we need to look into. The design you see is the design we have. (It's very close to the way Darwin's works.) We need to bugfix for sure, and patches are welcome; there's a lot of work and nonobvious behavior that's gone into the Darwin version, and the patches will need to clear a pretty high bar, but if you want to send a PR please do. |
@swift-ci please test and merge |
3 similar comments
@swift-ci please test and merge |
@swift-ci please test and merge |
@swift-ci please test and merge |
In this commit, I only fixed the
addDependency
bug. However, there is a critical bug https://bugs.swift.org/browse/SR-11333, exists from swift5.0 (I didn't check swift version < 5.0).I created a test case for OperationQueue and Operation which testing the dependency.