beast2 icon indicating copy to clipboard operation
beast2 copied to clipboard

Hiccups with preparing package for testing

Open jacklo225 opened this issue 1 year ago • 1 comments
trafficstars

Hi, I'm trying to compile my package and do some testing on a HPC by following the instructions from Writing A Beast 2.7 Package under the "Preparing your package for release" section. However, the beast2 compilation fails due to 6 tests failed (I think). Is it necessary for the beast2 compilation to be successful before compiling my package? Also, it is necessary to compile the beastFX package as well? My package doesn't include anything Beauti related, although we do run from beastfx.app.beast.BeastMain.

Thank you, Jack

     [java] Test run finished after 3013 ms
     [java] [         7 containers found      ]
     [java] [         0 containers skipped    ]
     [java] [         7 containers started    ]
     [java] [         0 containers aborted    ]
     [java] [         7 containers successful ]
     [java] [         0 containers failed     ]
     [java] [        10 tests found           ]
     [java] [         0 tests skipped         ]
     [java] [        10 tests started         ]
     [java] [         0 tests aborted         ]
     [java] [         4 tests successful      ]
     [java] [         6 tests failed          ]
     [java] 
     [java] Done

BUILD FAILED
/Users/jacklo/eclipse-workspace/beast2/build.xml:280: Java returned: 1

jacklo225 avatar May 01 '24 22:05 jacklo225

Thanks for pointing that out -- the default ant task for beast2 includes running junit tests, which can fail I believe due to randomization issues. These failures are harmless, and pass when run in a different environment. I suppose the solution to this is to change the default ant target in build.xml so tests are excluded.

There is no need to compile BeastFX, unless there are dependencies of your package to any of the BeastFX code.

rbouckaert avatar May 03 '24 00:05 rbouckaert