Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Hiccups with preparing package for testing #1149

Open
jacklo225 opened this issue May 1, 2024 · 1 comment
Open

Hiccups with preparing package for testing #1149

jacklo225 opened this issue May 1, 2024 · 1 comment

Comments

@jacklo225
Copy link

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 jacklo225 changed the title Hiccups with preparing package Hiccups with preparing package for testing May 1, 2024
@rbouckaert
Copy link
Member

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants