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

Workflow failed: GraalVM native tests (#207) #10184

Closed
github-actions bot opened this issue Jan 6, 2024 · 9 comments · Fixed by open-telemetry/opentelemetry-java#6134
Closed

Workflow failed: GraalVM native tests (#207) #10184

github-actions bot opened this issue Jan 6, 2024 · 9 comments · Fixed by open-telemetry/opentelemetry-java#6134

Comments

@github-actions
Copy link
Contributor

github-actions bot commented Jan 6, 2024

See GraalVM native tests #207.

Copy link
Contributor Author

github-actions bot commented Jan 7, 2024

See GraalVM native tests #208.

Copy link
Contributor Author

github-actions bot commented Jan 8, 2024

See GraalVM native tests #209.

Copy link
Contributor Author

github-actions bot commented Jan 9, 2024

See GraalVM native tests #210.

@laurit
Copy link
Contributor

laurit commented Jan 9, 2024

@jeanbisutti could you take a look. Probably caused by open-telemetry/opentelemetry-java#6095

Error: Error parsing reflection configuration in jar:file:/home/runner/.gradle/caches/modules-2/files-2.1/io.opentelemetry/opentelemetry-api/1.34.0/2a416e0747489363060880b19091840c1cf426f3/opentelemetry-api-1.34.0.jar!/META-INF/native-image/io.opentelemetry/opentelemetry-api/reflect-config.json:
first level of document must be an array of class descriptors
Verify that the configuration matches the schema described in the -H:PrintFlags=+ output for option ReflectionConfigurationResources.
Error: Use -H:+ReportExceptionStackTraces to print stacktrace of underlying exception

Perhaps this should be in resource-config.json not reflect-config.json?
@jack-berg this could require a patch release

@jeanbisutti
Copy link
Member

@laurit @jack-berg

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.

@jack-berg
Copy link
Member

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.

Copy link
Contributor Author

See GraalVM native tests #211.

Copy link
Contributor Author

See GraalVM native tests #212.

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 a pull request may close this issue.

3 participants