Skip to content

Fix java.mx test failure on ubuntu 26.04 - #9746

Open
mbien wants to merge 1 commit into
apache:deliveryfrom
mbien:fix-graalvm-again
Open

mbien wants to merge 1 commit into
apache:deliveryfrom
mbien:fix-graalvm-again

Conversation

@mbien

@mbien mbien commented Oct 23, 2026

Copy link
Copy Markdown
Member

it clones an EOL version of graalvm and mx and builds it, the recent Upuntu update broke it, again.

failures were on build-tools job and build system (build all tests). We removed the GraalVM job back in april (#9319).

targets delivery right now but I am not sure if there will be another RC.

@mbien mbien added this to the NB32 milestone Oct 23, 2026
@mbien mbien added tests MX [ci] enable "build tools" tests labels Oct 23, 2026

@matthiasblaesing matthiasblaesing left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Makes sense to me, but I think only java/java.mx.project/build.xml was intended for this commit. The rest of the changes seem to be picked up from a4be9f9.

@mbien

mbien commented Oct 24, 2026

Copy link
Copy Markdown
Member Author

oh thanks for noticing. not sure how this happened.

build clones an EOL version of graalvm and mx and builds it.
@mbien
mbien force-pushed the fix-graalvm-again branch from 65e104b to 5f23efe Compare October 24, 2026 19:24

@jtulach jtulach left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for the fix. If it makes the CI green, then it is a good fix.

@mbien

mbien commented Oct 26, 2026

Copy link
Copy Markdown
Member Author

btw this is the highest version i could update it to before graalvm switched to the modular version and each lang became a module. So the next time it fails we are stuck.

@jtulach

jtulach commented Oct 26, 2026

Copy link
Copy Markdown
Contributor

btw this is the highest version i could update it to before graalvm switched to the modular version and each lang became a module

  • I am not sure what do you mean by "lang become a module"?
  • I am using NetBeans 31 to work with https://github.com/oracle/graal/tree/graal-25.0.0 sources
    • it seems to work fine
  • I am certainly interested in using NetBeans to develop most recent GraalVM code
  • I can take a look and update to the newest GraalVM sources...

@mbien

mbien commented Oct 26, 2026

Copy link
Copy Markdown
Member Author

I am not sure what do you mean by "lang become a module"?

basically still #6925 (comment) i would guess since the version numbers line up - but I didn't investigate further.

Most of the NB's GraalVM specific tests were written expecting certain languages being supported by the grallvm dist out of the box and never got updated due to lack of interest. We keep hotfixing them when something fails.

I can take a look and update to the newest GraalVM sources...

yes please do and update test dependencies to more recent versions so that we get ahead of the test-failure curve and have some buffer again. From the test data perspective it probably also makes sense to test against something which is still supported by someone.

If possible: we should try to find a way how to not clone other repos during tests, e.g can this be tested differently?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

MX [ci] enable "build tools" tests tests

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants