-
Notifications
You must be signed in to change notification settings - Fork 10.5k
Concurrency/async_sequence_existential.swift is failing on main build #80582
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
Comments
The timing of the test failing does indicate that this is probably fallout from #80560. However, I have no idea what the difference is because the test failure output is pretty useless for debugging this, unfortunately. I ran full tests on this PR, which includes invoking this test on Windows and it passed. I have no idea what would be different about the Windows toolchain build that would make it sensitive to this. |
Here is the output with the recent changes:
I think the bug here is that the new output no longer says "error" at any point. Did that get eaten somewhere? |
Actually, this is the output after my latest changes designed to aid debugging this failure:
https://ci-external.swift.org/job/swift-main-windows-toolchain/1222/ The This AST dump wrapping behavior is really bad. |
I suggest we turn this test off in this configuration for now as this behavior is totally bizarre and the new output shows that nothing is actually broken except for how |
@compnerd do you have any insight into why this might be happening or have you seen anything like this before? Could it be something weird about how Windows handles flushing
|
Unblocks the Windows toolchain build, which is experiencing a weird symptom that causes this test to fail only in that context. The failure is tracked by swiftlang#80582.
Unblocks the Windows toolchain build, which is experiencing a weird symptom that causes this test to fail only in that context. The failure is tracked by swiftlang#80582.
Disabling the test for Windows here: #80663 |
The fix in swiftlang#80685 (using `-o` to write the output to a file, instead of relying on stdout/stderr redirection) seems to have addressed this issue on other bots. Resolves swiftlang#80582.
Description
On the main toolchain build, this test has been failing consistently for a few builds:
Swift(windows-x86_64) :: Concurrency/async_sequence_existential.swift
First failing build: https://ci-external.swift.org/job/swift-main-windows-toolchain/1216/
Additional information
Full failure log:
The text was updated successfully, but these errors were encountered: