Skip to content

Conversation

@hamishknight
Copy link
Contributor

Remove softTimeout since timeouts are no longer reported as issues, and make timedOut a soft error since faster runs could hit issues that aren't hit if they happen to timeout.

Remove `softTimeout` since timeouts are no longer reported as issues, and make `timedOut` a soft error since faster runs could hit issues that aren't hit if they happen to timeout.
@hamishknight hamishknight requested a review from ahoppen March 8, 2025 11:16
@hamishknight
Copy link
Contributor Author

@swift-ci please test

Copy link
Member

@ahoppen ahoppen left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thank you!

Comment on lines +58 to +60
/// The current use case for soft errors are timeouts, since it's possible
/// that it hits a failure on a faster run, which can lead to non-determinism
/// in matching XFAILs.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This comment is out-of-date now, right?

Copy link
Contributor Author

@hamishknight hamishknight Mar 8, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We still need soft errors for proper timeouts, since on faster runs a request can hit an error, and on slower runs they can hit a timeout. The current stress tester failure is because we have requests timing out, but sometimes they are able to finish and instead hit a known issue. So we need to have timeouts be able to match XFAILs.

@hamishknight hamishknight merged commit 2a877ee into swiftlang:main Mar 10, 2025
1 check passed
@hamishknight hamishknight deleted the timedout branch March 10, 2025 11:48
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

2 participants