-
Notifications
You must be signed in to change notification settings - Fork 214
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
Possible problem when resizing the daemon registry #695
Comments
Does at least the version mix we use on GutHub actions for work for you? - ie. ./mvnw instead of your local maven installation, GraalVM 22.2.0 for Java 17 set in JAVA_HOME |
No, this gives me the same error.
Reason: "A mapped byte buffer and the file mapping that it represents remain valid until the buffer itself is garbage-collected." It seems that at least on my environment (Windows 10 x64 with the initially mentioned Java version(s)) this doesn't work as desired b/c the byte buffer still exists... |
That makes sense, could you create a PR for that please ? |
Yes, sure. |
Following the instructions in the readme, I tried to locally build mvnd, but without success. A JUnit test fails:
This happens with Maven 3.8.6 and GraalVM 22.2.0 and either building the master branch or the tagged version 0.8.1.
Checking out 0.8.0, I also see a stracktrace on the console, but the unit test doesn't fail and the build continues:
I then thought, let's have a look at the code in my Eclipse IDE and try to find out what's going on:
Running the unit test class inside Eclipse with Adoptium OpenJDK 17.0.4.1, I see the same error message, but the unit test itself is marked as being executed successfully:
Funny:
With IBM's Semeru variant 17.0.4.1 instead of the Adoptium runtime, the same error message appears, but then the test is marked as faulty...
Does someone have any idea what is causing this strange behaviour?
The text was updated successfully, but these errors were encountered: