Skip to content
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

IPROTO-341 Transcode json array root object #284

Merged
merged 1 commit into from
Jul 3, 2024

Conversation

fax4ever
Copy link
Contributor

@tristantarrant
Copy link
Member

I tried running Infinispan's server/rest testsuite with a protostream snapshot compiled with this PR and I get the following failure:

SearchCountClusteredTest>MultipleCacheManagersTest.createBeforeClass:118->MultipleCacheManagersTest.callCreateCacheManagers:124->MultiNodeRestTest.createCacheManagers:51->MultiNodeRestTest.registerProtobuf:72 » MalformedJson Invalid JSON at [1,2]

@fax4ever
Copy link
Contributor Author

I tried running Infinispan's server/rest testsuite with a protostream snapshot compiled with this PR and I get the following failure:

SearchCountClusteredTest>MultipleCacheManagersTest.createBeforeClass:118->MultipleCacheManagersTest.callCreateCacheManagers:124->MultiNodeRestTest.createCacheManagers:51->MultiNodeRestTest.registerProtobuf:72 » MalformedJson Invalid JSON at [1,2]

Thank you @tristantarrant for checking it.
I did the same, basically running the snapshot with the Infinispan CI, but I didn't run the server tests module.
I'm checking it!

@fax4ever
Copy link
Contributor Author

@tristantarrant It seems that I have the same issue also if I run the server/test tests from the current main:

[ERROR] Errors: 
[ERROR]   EmbeddedRestSearchTest>MultipleCacheManagersTest.createBeforeClass:118->MultipleCacheManagersTest.callCreateCacheManagers:124->BaseRestSearchTest.createCacheManagers:111->BaseRestSearchTest.registerProtobuf:544 » MalformedJson Invalid JSON at [1,2]
[ERROR]   NonIndexedRestSearchTest>MultipleCacheManagersTest.createBeforeClass:118->MultipleCacheManagersTest.callCreateCacheManagers:124->BaseRestSearchTest.createCacheManagers:111->BaseRestSearchTest.registerProtobuf:544 » MalformedJson Invalid JSON at [1,2]
[INFO] 
[ERROR] Tests run: 2221, Failures: 0, Errors: 2, Skipped: 22
[INFO] 
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time:  01:52 min
[INFO] Finished at: 2024-06-26T10:18:15+02:00
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-surefire-plugin:3.2.5:test (defau

I'm not sure this is related to this contribution. There are probably some interleaving-cases that cause this error. Considering for instance that usually the JSON serializzation context is not thread safe, making it visible only on local runs but not on CI.

@ryanemerson
Copy link
Contributor

ryanemerson commented Jul 2, 2024

@fax4ever Do these failures occur every time on main? If so, I wonder why they're not being picked up by CI.

@fax4ever
Copy link
Contributor Author

fax4ever commented Jul 2, 2024

@fax4ever Do these failures occur every time on main? If so, I wonder why they're not being picked up by CI.

Good question. Just re-running the server rest tests on the current main and on this branch, I haven't seen the failures. :(

So at this point I would say that maybe that EmbeddedRestSearchTest and NonIndexedRestSearchTest are flaky tests...

Probably the test results depend on the particular interleaving on which the tests are concurrently executed, since the exception is the classic exception when we try to access to JSON serialization context concurrently.

@tristantarrant
Copy link
Member

The Infinispan testsuite passed for me. Merging

@tristantarrant tristantarrant merged commit 17dfdf0 into infinispan:main Jul 3, 2024
7 checks passed
@fax4ever
Copy link
Contributor Author

fax4ever commented Jul 3, 2024

Thanks @tristantarrant

@fax4ever fax4ever deleted the IPROTO-341 branch July 3, 2024 11:45
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants