zu-java holds install - #582
Merged
Merged
Conversation
tamnd/zu-java#15 added the clean-machine install job: a container with a JDK and Maven in it and nothing else, the quickstart lifted off the README, the dependency elements lifted off the same page, and a build against the artifacts that commit would publish. Two rows, the Panama provider on JDK 25 and the JNI provider on JDK 17, because installing on both is the claim this client makes that the others do not. It asserts no compiler, no libzu, no header and no ZU_LIBRARY before it starts, and it ends by taking the library artifact away and checking the failure names the line to add. That is 70 to 80 on practice. leaks, api-map and perf are what is left.
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.
tamnd/zu-java#15 landed the item the table words as a clean-machine install test, nightly, in a container holding the language runtime and nothing else.
A container with a JDK and Maven in it and nothing else. The script asserts what is absent before it does anything: no rustc, no cargo, no compiler of any kind, no libzu anywhere on the filesystem, no header, no pkg-config file, no
ZU_LIBRARY. Then it lifts the quickstart off the README character for character, lifts the dependency elements off the same page, writes a pom with nothing of ours in it, builds against the artifacts that commit would publish, and runs the program in an empty directory somewhere else on the machine, comparing what came out with the block the page says it prints.Two rows,
zudb-ffmon JDK 25 andzudb-jnion JDK 17, because installing on a JDK from 17 and a JDK from 25 over two different bindings out of one dependency is the claim this client makes that no other client of this engine makes. The last step takes the library artifact off the classpath and asserts the run fails naming the artifact to add, since a job that has only ever passed is a job nobody has watched fail.It found something on the way: from JDK 24 native access is granted by whoever starts the JVM, and the manifest attribute the jars carry speaks only for the jar that
java -jarnames, so the README paragraph claiming it covered the class path case was wrong and now says who grants it and where.zu-java goes 70 to 80 on practice. What is left there is
leaks, which is apparatus, andapi-mapandperf, which are reports the release collects.