-
Notifications
You must be signed in to change notification settings - Fork 300
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
ComplianceAuditlogTest to use signal/wait #1914
ComplianceAuditlogTest to use signal/wait #1914
Conversation
Recently with the build changes we have been seeing some increased test failures. Look at the biggest contributors its been the audit tests. By switching to the established `doThenWaitForMessage` this should improve test reliability considerably. Signed-off-by: Peter Nied <petern@amazon.com>
Before converting to a pull request that we merge, want to double check the CI test failures counts and make sure this was an improvement when run via GitHub Actions |
Assert.assertTrue(TestAuditlogImpl.messages.isEmpty()); | ||
Assert.assertTrue(validateMsgs(TestAuditlogImpl.messages)); | ||
} | ||
|
||
@Test | ||
public void testUpdatePerf() throws Exception { |
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.
This test has been removed because it doesn't verify any behavior of audit logs, all of the functionality has been commented out. Even with the commented out code added back in, that code does not include any verification or 'performance comparisons'.
Implementing perf tests is difficult to do well - I do not recommend that we invest or build on perf testing scenarios.
@Override | ||
public boolean isHandlingBackpressure() { | ||
return true; | ||
} | ||
|
||
public static class MessagesNotFoundException extends RuntimeException { |
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.
👏
Signed-off-by: Peter Nied <petern@amazon.com> (cherry picked from commit d507ebb)
Signed-off-by: Peter Nied <petern@amazon.com>
Signed-off-by: Peter Nied <petern@amazon.com> Signed-off-by: Stephen Crawford <steecraw@amazon.com>
Windows build and test support for 1.3 - Use most recent format of CI workflows from main - Backport #2206 - Supply workarounds for JDK8 incompatible APIs for Encoding / Pattern matching (Thanks @cwperks!) - Backport only freeport logic from #1638 - Backport #1758 - All updates to TestAuditlogImpl.java from main - #2180 - #1935 - #1920 - #1914 - #1829 - And Targeted test updates for ComplianceAuditlogTest and BasicAuditlogTest to keep up with TestAuditlogImpl.java updates Signed-off-by: Peter Nied <petern@amazon.com> Signed-off-by: Stephen Crawford <steecraw@amazon.com> Signed-off-by: Stephen Crawford <65832608+scrawfor99@users.noreply.github.com> Co-authored-by: Stephen Crawford <65832608+scrawfor99@users.noreply.github.com>
…pensearch-project#1915) Signed-off-by: Peter Nied <petern@amazon.com> (cherry picked from commit d507ebb) Co-authored-by: Peter Nied <petern@amazon.com>
Description
Recently with the build changes we have been seeing some increased test
failures. Look at the biggest contributors its been the audit tests.
By switching to the established
doThenWaitForMessage
this shouldimprove test reliability considerably.
Check List
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.