Test failure on macOS

[tmm1]

Running org.bytedeco.javacpp.BuilderTest
Builder
Generating /Users/tmm1/fancybits/javacpp/jnijavacpp.cpp
Generating /Users/tmm1/fancybits/javacpp/target/test-classes/org/bytedeco/javacpp/jniBuilderTest.cpp
Nothing generated for /Users/tmm1/fancybits/javacpp/target/test-classes/org/bytedeco/javacpp/jniBuilderTest.cpp
Builder
Generating /Users/tmm1/fancybits/javacpp/jnijavacpp.cpp
Generating /Users/tmm1/fancybits/javacpp/target/test-classes/org/bytedeco/javacpp/jniBuilderTest.cpp
Compiling /Users/tmm1/fancybits/javacpp/target/test-classes/org/bytedeco/javacpp/macosx-x86_64-ext2/libjniBuilderTest.dylib
clang++ -I/Library/Java/JavaVirtualMachines/jdk-9.jdk/Contents/Home/include -I/Library/Java/JavaVirtualMachines/jdk-9.jdk/Contents/Home/include/darwin /Users/tmm1/fancybits/javacpp/target/test-classes/org/bytedeco/javacpp/jniBuilderTest.cpp /Users/tmm1/fancybits/javacpp/jnijavacpp.cpp -march=x86-64 -m64 -O3 -Wl,-rpath,@loader_path/. -Wall -fPIC -dynamiclib -undefined dynamic_lookup -o libjniBuilderTest.dylib -framework JavaVM
Deleting /Users/tmm1/fancybits/javacpp/target/test-classes/org/bytedeco/javacpp/jniBuilderTest.cpp
Deleting /Users/tmm1/fancybits/javacpp/jnijavacpp.cpp
Loader
Tests run: 1, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 0.541 sec <<< FAILURE! - in org.bytedeco.javacpp.BuilderTest
testExtensions(org.bytedeco.javacpp.BuilderTest)  Time elapsed: 0.541 sec  <<< FAILURE!
java.lang.AssertionError
	at org.bytedeco.javacpp.BuilderTest.testExtensions(BuilderTest.java:70)

[saudet]

This is interesting, this isn't happening on my Mac... If you run just that test, what does your target/test-classes/org/bytedeco/javacpp/ contain after it fails?

[tmm1]

target/test-classes/org/bytedeco/javacpp
├── AdapterTest$SharedData.class
├── AdapterTest$UniqueData.class
├── AdapterTest.class
├── AdapterTest.h
├── BuilderTest.class
├── EnumTest$ByteEnum.class
├── EnumTest$EnumCallback.class
├── EnumTest$IntEnum.class
├── EnumTest$LongEnum.class
├── EnumTest$ShortEnum.class
├── EnumTest.class
├── EnumTest.h
├── IndexerTest.class
├── PointerTest$1.class
├── PointerTest$2.class
├── PointerTest$TestFunction.class
├── PointerTest.class
├── macosx-x86_64
│   ├── libjniAdapterTest.dylib
│   ├── libjniEnumTest.dylib
│   ├── libjniIndexerTest.dylib
│   └── libjniPointerTest.dylib
├── macosx-x86_64-ext1
│   └── libjniBuilderTest.dylib
└── macosx-x86_64-ext2
    ├── libjniBuilderTest.dylib
    ├── libjniEnumTest.dylib
    ├── libjniIndexerTest.dylib
    └── libjniPointerTest.dylib

[tmm1]

One thing I noticed elsewhere was some places are using darwin-x86_64 while others are using macosx-x86_64

[saudet]

That contains files from tests other than BuilderTest, could you run mvn clean test -Dtest=BuilderTest?

Where do you see "darwin" popping up?

[saudet]

I see this is Java 9, maybe they changed a couple of things there, I should check.

[tmm1]

The darwin I noticed was probably in the android toolchain paths and not related.

mvn clean test -Dtest=BuilderTest passes. mvn clean test also works fine.

mvn clean; mvn test also works, but then a subsequent mvn test fails.

[saudet]

Ah, yes, that's "normal", it's not expecting to have some of the files in place at the start of the test. I should fix that...

[tmm1]

I ran into this originally when I was just trying to mvn install after making some changes, and all of a sudden the tests were failing.

[saudet]

Finally fixed! Sorry about the trouble.