-
Notifications
You must be signed in to change notification settings - Fork 870
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
Workflow failed: GraalVM native tests (#207) #10184
Workflow failed: GraalVM native tests (#207) #10184
Comments
@jeanbisutti could you take a look. Probably caused by open-telemetry/opentelemetry-java#6095
Perhaps this should be in |
Yes, the file name should be resource-config.json. I am off today and could not access to my computer most of the day. There is also another GraalVM native issue with the last OTel Java release: open-telemetry/opentelemetry-java#6127 To be able to detect such native issues, I will try to add the possibility to execute some existing tests of the OTel Java repo both with a JVM runtime and with GraalVM native (the tests using Mockito could not be executed in the native mode). I have done this thing in the instrumentation repo for some instrumentation libraries and the OTel starter smoke tests. Today, in the OTel Java repo, from what I remember, there is only a GraalVM native test for JCTools calls. For a patch, the easiest thing to do would be to delete the json added file. |
We need to extend the graal test to be a more complete smoke test. It only tested a narrow portion of the SDK. We should extend it to include all the core SDK components which may use reflection or otherwise play poorly with graal. |
See GraalVM native tests #207.
The text was updated successfully, but these errors were encountered: