Skip to content

Adjust test_dateFromDoesntMutate expectations #2778

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
Apr 28, 2020

Conversation

lxbndr
Copy link
Contributor

@lxbndr lxbndr commented Apr 27, 2020

CI runs in UTC time zone, and this affects the description of TimeZone being tested.

CC @compnerd

CI runs in UTC time zone, and this affects the description of TimeZone
being tested.
@compnerd
Copy link
Member

Ugh, that’s super . Nice catch!

@compnerd
Copy link
Member

@swift-ci please test Linux platform

1 similar comment
@compnerd
Copy link
Member

@swift-ci please test Linux platform

@compnerd
Copy link
Member

@compnerd
Copy link
Member

NSOperation tests are still flakey, but that isn't related to this. LGTM.

@compnerd compnerd merged commit c971e6f into swiftlang:master Apr 28, 2020
@lxbndr lxbndr deleted the does-date-from-mutate branch April 28, 2020 18:00
@lxbndr
Copy link
Contributor Author

lxbndr commented Apr 28, 2020

NSOperation tests are still flakey, but that isn't related to this. LGTM.

Oh, interesting. It is from the new test set. Never stepped on this before.

Operation notifies about completion a moment before it is removed from Queue. I guess it is expected behavior, and check in the test just fires too early. Queue needs some time to remove finished Operation. Looks like we need to adjust test to wait a little before assertion check.

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.

2 participants