-
Notifications
You must be signed in to change notification settings - Fork 10.5k
🛑 DON'T MERGE [test] Fix source-stability test and revert #18793 #18794
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
Conversation
@swift-ci please test |
@@ -1,4 +1,6 @@ | |||
/* FIXME: Bogus */ | |||
Struct DictionaryIterator has generic signature change from <Key, Value where Key : Hashable> to <Element> | |||
Struct SetIterator has generic signature change from <Element where Element : Hashable> to <Key, Value> |
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.
Wait, this seems backwards? Why would they switch like this?
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.
They didn't -- these became typealiases to Dictionary.Iterator and Set.Iterator, respectively, but they kept the same generic signatures.
@nkcsgexi Is this right?
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.
The correct diags are actually like these:
-Struct DictionaryIterator has generic signature change from <Key, Value where Key : Hashable> to
-Struct SetIterator has generic signature change from to <Key, Value>
+Struct DictionaryIterator has generic signature change from <Key, Value where Key : Hashable> to <Key, Value>
+Struct SetIterator has generic signature change from to
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.
I copy & pasted the ones in this PR from my own test logs, with no edits -- is it possible the api-digester output is somehow nondeterministic?
Build failed |
Interesting -- in this build, it reverted to a less surprising (although still spurious) change. |
@swift-ci test |
hmm, that'll be a bug of the tool. nondeterministic outputs will manifest as a flaky test. could we run the CI multiple times and see? |
We'll see a second run soon; the new CI build is almost done compiling. |
It looks like api-digester definitely has nondeterministic output -- I've seen four different variants in six local test runs:
|
Yep, the test has passed in the current build, despite the earlier failure:
|
Thanks, I'll investigate what's going on. |
hmm, i cannot reproduce the nondeterministic output issue locally. We should run the swift-ci multiple times here to see if it reproduces. |
oh, i can reproduce this issue with more runs. It seems |
See #18811 for the correct fix. |
rdar://problem/43425867