-
Notifications
You must be signed in to change notification settings - Fork 282
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
[BUG] Unexpected Coverage Changes on SelfRefreshingKeySet, SecurityInterceptor and SecuritySSLNettyTransport #3137
Comments
[Triage] Thank you for filing this issue @peternied. Based on the provided checklist, I will label this issue as actionable and triaged. |
@peternied I Started looking into it. Please let me know if you have any useful information that I can use to address this. |
@davidosorno I'm excited to see these get fixed, In the descriptions 'checklist' is most of my thoughts - we can dig in more with a pull request - I'd recommend to create a draft, happy to review if you've got questions. |
@peternied I created a draf PR for this issue, please take a look at it and let me know what you think. |
There are some cases that use datetime that were causing code coverage flutuations depending on when the tests are run. - Related opensearch-project#3137 Signed-off-by: Peter Nied <[email protected]>
There are some cases that use datetime that were causing code coverage flutuations depending on when the tests are run, fixed this by adding a date provider and new unit tests. - Related opensearch-project#3137 Signed-off-by: Peter Nied <[email protected]>
The second and third check boxes should be all set shortly. |
### Description [Describe what this change achieves] This change increases code coverage for the SecuritySSLNettyTransport class. In the middle of 12/23, a few unit tests were added to give coverage to different parts of the class. This change builds on these existing changes. ### Issues Resolved Box three of #3137 Signed-off-by: Stephen Crawford <[email protected]>
…#3953) ### Description [Describe what this change achieves] This change increases code coverage for the SecuritySSLNettyTransport class. In the middle of 12/23, a few unit tests were added to give coverage to different parts of the class. This change builds on these existing changes. ### Issues Resolved Box three of opensearch-project#3137 Signed-off-by: Stephen Crawford <[email protected]>
What is the bug?
There are several classes that are seeing random behavior in code coverage reports. Test should be added/modified to ensure these code paths are always exercised - keeping codecov results useful.
Codecov [Report link]
Codecov [Unexpected Coverage Changes]
How can one reproduce the bug?
What is the expected behavior?
Code coverage should not fluctuate, testing should be deterministic and 'exhaustive'
Do you have any additional context?
This is causing code coverage failures on many pull requests and code is being merged without all checks passing regularly.
The text was updated successfully, but these errors were encountered: