-
Notifications
You must be signed in to change notification settings - Fork 183
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
add checks to existing unit tests #1104
Conversation
What would you like added to change log since this is just unit test changes and not overly complicated changes. Given the minor changes, not sure why so many red 'X's are showing up. |
We can skip the changelog, but not sure what's up with the integ test failure.
Is it caused by this import which attempts to bring the kitchen sink from OpenSearch?
|
Is there a different GetRequest I should be importing? I have all the amazon cruft in my environment so does not matter to me. I think the point is that the GetRequest is not the same on main as 2.x. It is the encoding of the ID that we ultimately care about (my project) and the RefreshRequest is insufficient to test the ID encoding. Probably similar failure with DeleteByQueryRequest too but maybe fixing GetRequest (or its root cause) will fix the DBQR as well. |
I take it back. My gradle build in eclipse is showing 3 errors in the integrations tests but it looks like eclipse is java 8 while these tests are in src/test/java11 so I am going to say that it local to me. Still the changes I made should not make any difference to your build beyond importing from core somehow being evil. |
The failures were completely unrelated to the changes in this PR, just got unlucky and they ran at the exact time a release of AWS SDK was happening, so got some of the newer version libraries while their dependencies hadn't been pushed to maven yet. |
Only failures now are DCO and spotless check. |
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.
@Xtansia bah! Thanks for digging into it.
@al-niessner Please fix the spotless linter and DCO (git commit --amend -s
and force push) and let's merge this test and see it fail in 2.x?
Sorry I see two MAC build fails and DCO. What is spotless? |
Check out https://github.com/opensearch-project/OpenSearch/blob/main/DEVELOPER_GUIDE.md#java-language-formatting-guidelines, we use the same linter here.
You should be able to |
Oh, I see. I thought MacOS-latest was some attempt to build the latest main branch on a MacOS. Anyway, followed directions in the output and used gradlew to fix it. |
One for EndpointTest that checks for the GetRequest.id() being correctly encoded. One for PathEncodingTesst to verify that ":" is being encoded. Updated for spotless. Signed-off-by: Al Niessner <Al.Niessner@xxx.xxx>
One for EndpointTest that checks for the GetRequest.id() being correctly encoded. One for PathEncodingTesst to verify that ":" is being encoded. Updated for spotless. Signed-off-by: Al Niessner <Al.Niessner@xxx.xxx> Co-authored-by: Al Niessner <Al.Niessner@xxx.xxx> (cherry picked from commit c098d8b) Signed-off-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
Description
Shows that 'a:b:c::2.0' works on main but not 2.x branches.
Issues Resolved
#1103
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.