| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Signed-off-by: Tim Perry <pimterry@gmail.com>
There was a problem hiding this comment.
lgtm
good catch
Sorry, something went wrong.
|
Fast-track has been requested by @mcollina. Please 👍 to approve. |
Sorry, something went wrong.
Sorry, something went wrong.
Sorry, something went wrong.
Sorry, something went wrong.
Signed-off-by: Tim Perry <pimterry@gmail.com> PR-URL: #64673 Reviewed-By: Matteo Collina <matteo.collina@gmail.com> Reviewed-By: Luigi Pinca <luigipinca@gmail.com>
Signed-off-by: Tim Perry <pimterry@gmail.com> PR-URL: #64673 Reviewed-By: Matteo Collina <matteo.collina@gmail.com> Reviewed-By: Luigi Pinca <luigipinca@gmail.com>
| Back | FazBrowse Home | New Git URL |
Fix a flaky test (failing yesterday) introduced recently in #64427.
This is effectively two tests running in parallel against a single server. The second test shuts down the server when it finishes, assuming that this means everything is done, but if the first test runs slowly it may not complete before that happens.
Adding a setTimeout manually around the first test block to simulate this recreates the same error as in CI.
Nice easy fix: use a Countdown to wait for both tests before closing the server, so there's no interdependency.