Skip to content
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

Issue #5062 - fix flaky test KeyStoreScannerTest.testKeystoreRemoval() #5065

Merged
merged 1 commit into from
Jul 23, 2020

Conversation

lachlan-roberts
Copy link
Contributor

Closes #5062

KeyStoreScannerTest now uses manual scanning to avoid timing issues.

… timing issues

Signed-off-by: Lachlan Roberts <lachlan@webtide.com>
LOG.debug("scanning");

_scanner.scan();
_scanner.scan();
Copy link
Contributor Author

Choose a reason for hiding this comment

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

We scan twice here because the Scanner won't report changes on the first scan, it wants to make sure the file is "stable" before it reports the change, so it needs two consecutive scans with the file unchanged.

@lachlan-roberts lachlan-roberts linked an issue Jul 21, 2020 that may be closed by this pull request
@lachlan-roberts lachlan-roberts merged commit 6b37983 into jetty-9.4.x Jul 23, 2020
@lachlan-roberts lachlan-roberts deleted the jetty-9.4.x-5062-testKeystoreRemoval branch July 23, 2020 07:29
@joakime joakime added the Test label Jul 23, 2020
@joakime joakime added this to In progress in Jetty 9.4.31 via automation Jul 23, 2020
@joakime joakime moved this from In progress to Done in Jetty 9.4.31 Jul 23, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
No open projects
Jetty 9.4.31
  
Done
Development

Successfully merging this pull request may close these issues.

flaky test KeystoreScannerTest.testKeystoreRemoval()
3 participants