Tests occasionally (??) do nothing

[galexv]

Often, but not every time, running make test on Cloudbees under Jenkins results in:

ERROR: Step ‘Publish JUnit test result report’ failed: None of the test reports contained any result
[...]
Finished: FAILURE

and indeed, looking into the test log shows

Start testing: Feb 27 13:19 EST
----------------------------------------------------------
1/6 Testing: default_modelTest
1/6 Test: default_modelTest
Command: "/scratch/jenkins/workspace/maxent-alpscore/test/default_modelTest" "--gtest_output=xml:default_modelTest.xml"
Directory: /scratch/jenkins/workspace/maxent-alpscore/test
"default_modelTest" start time: Feb 27 13:19 EST
Output:
----------------------------------------------------------
Running main() from gtest_main.cc
[==========] Running 0 tests from 0 test cases.
[==========] 0 tests from 0 test cases ran. (0 ms total)
[  PASSED  ] 0 tests.
<end of output>
Test time =   0.05 sec
----------------------------------------------------------
Test Passed.
"default_modelTest" end time: Feb 27 13:19 EST
"default_modelTest" time elapsed: 00:00:00

See attached Maxent_LastTest_20180227.log

[ryanlevy]

Hmm any thoughts on why this is? Could it be due to the fact we use a new gtest compilation for each test file? I think somewhere in ALPSCore it was figured out how to only do it once, I should probably port that over as well

[egull]

I don't have a good feeling for it. But for the supported open source codes, we could move to Travis CI instead (we're going to do this for Hiroshi's code, too). What do you think?

[ryanlevy]

I forgot to reference it here, but in commit d0108dae870c4cc90919ab8a360e8a81c0839900 I added a Travis CI script