-
Notifications
You must be signed in to change notification settings - Fork 2.7k
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
Fix broken Feature#runtimeInitializedPackages method #30027
Fix broken Feature#runtimeInitializedPackages method #30027
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM @geoand, thanks !
Good catch by the way, this should have been caught by the CI though. Do you think you could add a test for it as well?
The only way I can think of to do this would be to have some custom extension that generates the build item. I think it's a worthy addition :) |
Failing Jobs - Building 6ac08e3
Full information is available in the Build summary check run. Failures⚙️ JVM Tests - JDK 17 MacOS M1 #- Failing: extensions/micrometer/deployment
! Skipped: extensions/micrometer-registry-prometheus/deployment extensions/quartz/deployment extensions/scheduler/deployment and 21 more 📦 extensions/micrometer/deployment✖
|
Perhaps you can reuse/extend this Lines 465 to 468 in f096001
|
That integration test should actually be run when in the |
@famod any chance you can take a look at |
There seems to be another issue with the test. In the mandrel nightly CI runs (that are not "incremental") the test is included in |
That's weird because when I ran the test manually |
Are these native tests though, do you see a native-image being generated? Can you try with |
Yes, I saw the native binary being built with my fix while seeing the error mentioned in quarkiverse/quarkus-neo4j#115 without it |
I tried locally on 4397da6 with |
Note the use of |
OK, that seems to be an issue in the CI as well (both in the mandrel workflows and the quarkus), which run the tests using:
|
Yeah, that's certainly part of the problem. The other part is that |
I opened #30035 and graalvm/mandrel#462 to fix this.
For this part I can't help much but it looks like the test is correctly added when running on the https://github.com/quarkusio/quarkus/actions/runs/3755597705/jobs/6381059498#step:12:15 |
Ah, that's nice! |
Relates to: quarkiverse/quarkus-neo4j#115