Skip to content

Remove previous hack for SR-5206 #1259

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

Merged
merged 1 commit into from
Oct 12, 2017

Conversation

itaiferber
Copy link
Contributor

What's in this pull request?
Remove remaining references to SR-5206 hack by bringing the implementation inline with the Foundation overlay.

Applies swiftlang/swift#11315 to swift-corelibs-foundation. This will go into the swift-4.0-branch as well.

Remove remaining references to SR-5206 hack by bringing the
implementation inline with the Foundation overlay.
@itaiferber itaiferber requested a review from phausler October 11, 2017 20:45
@itaiferber
Copy link
Contributor Author

@swift-ci Please test

@alblue
Copy link
Contributor

alblue commented Oct 12, 2017

@swift-ci please test

@alblue
Copy link
Contributor

alblue commented Oct 12, 2017

Looks like these failures aren't related - @spevans it seems to be to do with the NSLock tests?

Test Case 'TestNSLock.test_lockWait' started at 2017-10-12 11:06:43.671
TestFoundation/TestNSLock.swift:57: error: TestNSLock.test_lockWait : XCTAssertTrue failed - 
TestFoundation/TestNSLock.swift:58: error: TestNSLock.test_lockWait : XCTAssertTrue failed - 
TestFoundation/TestNSLock.swift:59: error: TestNSLock.test_lockWait : XCTAssertTrue failed - 
TestFoundation/TestNSLock.swift:60: error: TestNSLock.test_lockWait : XCTAssertTrue failed - 
Test Case 'TestNSLock.test_lockWait' failed (0.0 seconds)

@spevans
Copy link
Contributor

spevans commented Oct 12, 2017

@alblue, yes I think there might be a bug in the lock test unrelated to this change. I think I can see the issue so I'll create a PR which should hopefully fix it.

@spevans
Copy link
Contributor

spevans commented Oct 12, 2017

@alblue hopefully #1261 should fix it. This PR looks unrelated it looks like a testing on a loaded CI server issue.

@alblue
Copy link
Contributor

alblue commented Oct 12, 2017

@swift-ci please smoke test

1 similar comment
@alblue
Copy link
Contributor

alblue commented Oct 12, 2017

@swift-ci please smoke test

@itaiferber
Copy link
Contributor Author

@swift-ci Please clean test

@alblue
Copy link
Contributor

alblue commented Oct 12, 2017

@swift-ci please test

@alblue
Copy link
Contributor

alblue commented Oct 12, 2017

@itaiferber according to @shahmishal the foundation build doesn't understand smoke tests or clean tests ... so I've kicked it off again with the please test :)

@itaiferber
Copy link
Contributor Author

@alblue Ah, right — I never remember which project supports what. Thanks!

@alblue
Copy link
Contributor

alblue commented Oct 12, 2017

@itaiferber that's ok, I only found out about half an hour ago too :)

@itaiferber itaiferber merged commit 799fb06 into swiftlang:master Oct 12, 2017
@itaiferber itaiferber deleted the fix-sr-5206-hack branch October 12, 2017 19:05
@itaiferber
Copy link
Contributor Author

I just looked in the swift-4.0-branch but it looks like these changes are already in there. ¯\(ツ)/¯ Less work for me, I guess...

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 this pull request may close these issues.

3 participants