Karl Lessard
Karl Lessard
> It seems to be a maven/surefire issue, manually running `java` with a test class works fine. Make sure Maven is using the version of Java you want to test...
If unit-testing multi-release JAR is something too complicated, let's skip it, anyway there is no code being really tested but only a Maven config.
Closing for lacking details on the issue
Just to let you know that I've just merge this [PR](https://github.com/tensorflow/java/pull/303) to upgrade the current 0.4.0 snapshots to TensorFlow 2.5. It should be ready to be tested out in about...
Ok, we had some trouble building the new snapshots with TF2.5 but it is ready now to be used for testing.
@rnett any quick idea?
Another concern I have by running spotless by default is that all PRs we receive include a tons of changes unrelated to the feature being added, I've shared [this comment](https://github.com/tensorflow/java/pull/328#issuecomment-852265645)...
@whalefa1I , it looks like you are still using version `0.2.0`, some memory leak issues have been fixed in `0.3.1`, can you give try the original code with this version?...
@maziyarpanahi , @wolliq , I suppose you work with String tensors, right? Something that has changed drastically between TF Java 0.2.0 and 0.3.1 is how string tensors are allocated by...
Well something else major that has change is that now the tensor memory (of all types) is automatically mapped in the JVM, while in 0.2.0 it was only done when...