Repository navigation
Build MobilitySpark without a warning - #63
Merged
estebanzimanyi merged 1 commit intoOct 1, 2026
Merged
Conversation
MeosMemory frees a pointer MEOS returns through com.kenai.jffi.MemoryIO.freeMemory, which calls the system free(). jffi is the native layer jnr-ffi runs on, so it shares the classloader of every MEOS call inside Spark, and MobilitySpark calls no internal JDK API. The pom pins org.apache.yetus:audience-annotations, which ZooKeeper reads under Spark, to 0.15.0, the first release whose parent POM declares no system-scope jdk.tools on lib/tools.jar. 0.5.0, the version Spark 3.5.1 brings, declares it, and no JDK from 9 on ships that file. The Maven workflow refuses a build that prints a warning: a [WARNING] line from Maven or a WARNING: line from JUnit or the JVM during the tests. Measured. MemoryIO.freeMemory is final and calls Foreign.freeMemory, whose native entry in jffi 1.3.13 jumps to free. Against MobilityDB eb8f601a29, the catalog of MEOS-API 0a54dfe443 and the generator and jar of JMEOS main 8783e1ca, mvn clean test under Maven 3.9.16, the version of the ubuntu-24.04 runner, prints no warning line and the 22 tests pass. Main prints nine: eight sun.misc.Unsafe in MeosMemory.java and "2 problems were encountered while building the effective model for org.apache.yetus:audience-annotations:jar:0.5.0".
estebanzimanyi
force-pushed
the
build/zero-warnings
branch
from
October 1, 2026 18:11
e0b0411 to
07a25af
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
MeosMemory frees a pointer MEOS returns through com.kenai.jffi.MemoryIO.freeMemory, which calls
the system free(). jffi is the native layer jnr-ffi runs on, so it shares the classloader of
every MEOS call inside Spark, and MobilitySpark calls no internal JDK API.
The pom pins org.apache.yetus:audience-annotations, which ZooKeeper reads under Spark, to
0.15.0, the first release whose parent POM declares no system-scope jdk.tools on lib/tools.jar.
0.5.0, the version Spark 3.5.1 brings, declares it, and no JDK from 9 on ships that file.
The Maven workflow refuses a build that prints a warning: a [WARNING] line from Maven or a
WARNING: line from JUnit or the JVM during the tests.
Measured. MemoryIO.freeMemory is final and calls Foreign.freeMemory, whose native entry in
jffi 1.3.13 jumps to free. Against MobilityDB eb8f601a29, the catalog of MEOS-API 0a54dfe443
and the generator and jar of JMEOS main 8783e1ca, mvn clean test under Maven 3.9.16, the version
of the ubuntu-24.04 runner, prints no warning line and the 22 tests pass. Main prints nine: eight
sun.misc.Unsafe in MeosMemory.java and "2 problems were encountered while building the effective
model for org.apache.yetus:audience-annotations:jar:0.5.0".