-
Notifications
You must be signed in to change notification settings - Fork 24.9k
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
Make GeoIpDownloaderIT.testInvalidTimestamp more robust #75330
Conversation
Pinging @elastic/es-core-features (Team:Core/Features) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, I left one super minor comment
client().admin().cluster() | ||
.prepareUpdateSettings() | ||
.setPersistentSettings(Settings.builder() | ||
.put("ingest.geoip.database_validity", (String) null)) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Minor nit:
.put("ingest.geoip.database_validity", (String) null)) | |
.putNull("ingest.geoip.database_validity") |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice, I haven't seen that method before, I've update it in other places in this test as well
@elasticmachine update branch |
This change adds additional assertion in GeoIpDownloaderIT.testInvalidTimestamp which makes sure that validity checks work both ways (so going out of validity and back) and it should fix race in cleanUp method leading to occasional failures. Closes elastic#75221 Closes elastic#74358
This change adds additional assertion in GeoIpDownloaderIT.testInvalidTimestamp which makes sure that validity checks work both ways (so going out of validity and back) and it should fix race in cleanUp method leading to occasional failures. Closes elastic#75221 Closes elastic#74358
… (#75353) * Make GeoIpDownloaderIT.testInvalidTimestamp more robust (#75330) This change adds additional assertion in GeoIpDownloaderIT.testInvalidTimestamp which makes sure that validity checks work both ways (so going out of validity and back) and it should fix race in cleanUp method leading to occasional failures. Closes #75221 Closes #74358 * compilation fix Co-authored-by: Przemko Robakowski <[email protected]>
#75354) * Make GeoIpDownloaderIT.testInvalidTimestamp more robust (#75330) This change adds additional assertion in GeoIpDownloaderIT.testInvalidTimestamp which makes sure that validity checks work both ways (so going out of validity and back) and it should fix race in cleanUp method leading to occasional failures. Closes #75221 Closes #74358 * compilation fix Co-authored-by: Przemko Robakowski <[email protected]>
This change adds additional assertion in GeoIpDownloaderIT.testInvalidTimestamp which makes sure that validity checks work both ways (so going out of validity and back) and it should fix race in cleanUp method leading to occasional failures. Closes elastic#75221 Closes elastic#74358
This change adds additional assertion in
GeoIpDownloaderIT.testInvalidTimestamp
which makes sure that validity checks work both ways (so going out of validity and back) and it should fix race incleanUp
method leading to occasional failures.Closes #75221
Closes #74358