-
Notifications
You must be signed in to change notification settings - Fork 1.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
[BUG] Test case org.opensearch.action.admin.cluster.shards.CatShardsRequestTests.testSerializationWithOlderVersionsParametersNotSerialized fails with NPE #16580
Comments
@gargharsh3134 could you please take a look? caused by #14641 / #16455 |
Blocks #16571 |
The test creates a string array: Line 96 in 99a9a81
But the elements of the array are null, and thus fail when attempting to serialize for transport. The failure didn't occur on 3.0.0 or 2.8.0 because the previous version didn't pass the "on or after" check and never attempted to serialize the array of nulls. It's failing on 2.8.1 because the previous version is 2.8.0 and does meet the earlier version on or after 2.8.0, and reads the string array. Fix is probably populating that string array with some random strings, similar to how is done in another test in the same class: Lines 42 to 45 in 99a9a81
|
Describe the bug
The test case
org.opensearch.action.admin.cluster.shards.CatShardsRequestTests.testSerializationWithOlderVersionsParametersNotSerialized
fails with NPE:Related component
Other
To Reproduce
Pull
https://github.com/opensearch-project/OpenSearch/pull/16571
and run./gradlew ':server:test' --tests "org.opensearch.action.admin.cluster.shards.CatShardsRequestTests.testSerializationWithOlderVersionsParametersNotSerialized"
Expected behavior
The test case should pass
Additional Details
Plugins
Please list all plugins currently enabled.
Screenshots
If applicable, add screenshots to help explain your problem.
Host/Environment (please complete the following information):
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: