Skip to content

Conversation

@bnickel
Copy link
Contributor

@bnickel bnickel commented Aug 29, 2025

Our CI system runs on up to 4 parallel simulators, putting the CPU under higher-than-average stress levels. As a result, we get occasional flakiness when toEventually, toAlways and toNever encounter a blocked run loop.

In this scenario, it doesn't really make sense for toAlways and toNever to fail, since the conditions weren't violated in the extended timeout window.

This change addresses that issue by resolving with .timeOut for continous AsyncMatchStyles even when the main loop is blocked.

Checklist - While not every PR needs it, new features should consider this list:

  • Does this have tests?
  • Does this have documentation?
  • Does this break the public API (Requires major version bump)?
  • Is this a new feature (Requires minor version bump)?

@younata
Copy link
Member

younata commented Oct 1, 2025

Looks like this is failing to build on linux with swift 6.0+

Edit: No, that's your previous PR, which I merged without checking CI. That's on me.

@younata younata merged commit 1ee0178 into Quick:main Oct 1, 2025
13 of 20 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants