-
Notifications
You must be signed in to change notification settings - Fork 10.5k
DNM: Add -Rmodule-interface-rebuild to startOnMainActor #64653
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
Add remark to see why we're rebuilding from the swiftinterface occasionally, instead of using the perfectly good swiftmodule for the stdlib.
@swift-ci please test |
We can merge if I don't catch it the first time so that we get some parallel data collection action going. |
llvm-lit isn't showing me the output from stdout, so I don't think we're getting the remarks when things fail. Redirect the stdout to stderr so llvm-lit shows _all the things_.
@swift-ci please smoke test |
Windows failure:
|
Bah humbug. Right test, wrong failure. |
@compnerd managed to get it to reproduce reliably enough to get the remarks. It's the issue @bnbarham and I talked about yesterday. The indexer is pulling the module from the cache that was built from the swiftinterface instead of the swiftmodule in In case it's useful CC: @xymus
|
Add remark to see why we're rebuilding from the swiftinterface occasionally, instead of using the perfectly good swiftmodule for the stdlib.
This is starting to affect the Windows CI now. Hopefully I get lucky and can trigger the failure first try.
The other workaround is here, to produce the
private.swiftinterface
. We're supposed to prefer digging things out of the swiftmodule for the stdlib though, so that fix will just mask the issue for now.