-
Notifications
You must be signed in to change notification settings - Fork 244
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
testWhitespaceLinterPerformance is flaky on Windows #939
Comments
Synced to Apple’s issue tracker as rdar://145139964 |
Let's skip `testWhitespaceLinterPerformance` on Windows until someone with more linter performance insights can craft a real fix for #939.
When executing in Swift CI, run the block to make sure it doesn't hit any assertions because we don't look at performance numbers in CI and CI nodes can have variable performance characteristics if they are not bare-metal. Anywhere else, run XCTest's `measure` function to measure the performance of the block. Fixes swiftlang#939 rdar://145139964
Thanks for addressing this swiftly :) Flakes were still happening tonight. From https://ci-external.swift.org/job/swift-PR-windows/36728/ on the bot checks out eeb2850 which has the patches. |
Do you have an example of this test failing after these patches? Looking at the failing builds from 36728 onwards, they were all real failures in tests well before this test runs. This test is also disabled completely in CI now, so I'd be very surprised if any flakiness was still caused by it. |
Ah, I missed to confirm that bots are looking good from 36728 onwards. Yes. It had not finished when I checked this morning. |
Oops, it happened again! https://ci-external.swift.org/job/swift-PR-windows/36802/ Please reopen this ticket. I am lacking permission. Attaching the full log before it gets wiped: swift-PR-windows-36802.log Check-out was good:
Back with the same error:
@ahoppen Your change dropped my workaround, so I'd leave further investigation to you. |
Test output:
This causes a lot of noise in PR-testing. Failures within the last 36 hours were:
https://ci-external.swift.org/job/swift-PR-windows/36617/
https://ci-external.swift.org/job/swift-PR-windows/36620/
https://ci-external.swift.org/job/swift-PR-windows/36623/
https://ci-external.swift.org/job/swift-PR-windows/36649/
https://ci-external.swift.org/job/swift-PR-windows/36660/
https://ci-external.swift.org/job/swift-PR-windows/36668/
https://ci-external.swift.org/job/swift-PR-windows/36671/
The underlying issue is that Swift.org bots for the mainline Windows toolchain are lacking coverage, because developers have no access to the configuration. LLDB tests are one example for this (see swiftlang/swift#79020). They run in PR-testing, but not in mainline testing and thus we have no good monitoring for flakes.
The text was updated successfully, but these errors were encountered: