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
NettyBlockHoundIntegrationTest.testBlockingCallsInNettyThreads fails with JDK 13 #9738
Comments
@bsideup can you have a look ? It works with all other JDK version that we use on the CI :/ |
@normanmaurer JDK13+ requires a flag ( We're still investigating what to do about it, since it was a behaviour change in OpenJDK's instrumentation logic... |
@bsideup I see... I will add these to the java13 profile then for now. |
@bsideup this did not work :(
|
@normanmaurer on it, trying locally |
@bsideup thanks... PRs welcome :) |
@normanmaurer interesting. It works when I run BlockHound's tests with Java 13 but fails in Netty. Trying to find how to check that the flag is actually set in the tests' JVM... |
status update: Checking whether it is a problem with BlockHound or with the whitelisting we do in the integration, so that the call is instrumented but not reported update 2: |
Ok, it seems that Maven was using an old SNAPSHOT from pre-BlockHound era, this is why running it with IDEA was giving me a positive result but with Maven I was getting errors. I submitted #9742 with a simple profile-based fix, and will submit another one with a test checking that |
…der` Motivation: If something is mis-configured, the "main" test will fail but it is unclear whether it fails because the integration does not work or it wasn't applied at all. Also see: netty#9738 (comment) Modifications: This change adds a test that uses the same mechanism as BlockHound does (`ServiceLoader`) and checks that `NettyBlockHoundIntegration` is present. Result: It is now clear whether the integration is not working or it wasn't loaded at all.
Ok, I think now we're good :) #9743 is an optional addition to make it easier to debug issues in future, since I spent quite some time fighting with JDK13 while the problem was in my Maven setup and Maven's vision on how modular projects should be built 😅 |
…der` (#9743) Motivation: If something is mis-configured, the "main" test will fail but it is unclear whether it fails because the integration does not work or it wasn't applied at all. Also see: #9738 (comment) Modifications: This change adds a test that uses the same mechanism as BlockHound does (`ServiceLoader`) and checks that `NettyBlockHoundIntegration` is present. Result: It is now clear whether the integration is not working or it wasn't loaded at all.
…der` (#9743) Motivation: If something is mis-configured, the "main" test will fail but it is unclear whether it fails because the integration does not work or it wasn't applied at all. Also see: #9738 (comment) Modifications: This change adds a test that uses the same mechanism as BlockHound does (`ServiceLoader`) and checks that `NettyBlockHoundIntegration` is present. Result: It is now clear whether the integration is not working or it wasn't loaded at all.
The text was updated successfully, but these errors were encountered: