-
Notifications
You must be signed in to change notification settings - Fork 238
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
Jenkins problems #335
Comments
I created a new multi-branch configuration that should be better for what we are trying to accomplish. This should fix issues 2 and 3. For the reproducibility of errors, that will probably take both setting the random seed parameter in Hail for all random tests and getting Jenkins to give better error messages. |
heh, careful with '#' on github |
See the random seed specification in #357 . Gradle will say the random seed at the top of the log if tests are run with gradle. Spec.check will also print it out (for use in IntelliJ). You can either specify using Spec.check(seed = Option(5)) or with the Java properties: |
All of these have been resolved. |
Three things:
http://hail-ci.broadinstitute.org:8080/job/Hail%20-%20Test%20All%20Branches/116/
of master, revision 6d5fe39, failed several test cases, but I wasn't able to reproduce it on my laptop. Can we get more detailed logs, either by default or in another file, so we can debug build irreproducible build failures? Custom log4j properties for gradle might be a solution.
http://hail-ci.broadinstitute.org:8080/job/Hail%20-%20Test%20All%20Branches/119/
which is labeled "rebuild of #116", but it is a build of a different branch, origin/tp_dbnsfp_bug and a different revision. What's going on?
The text was updated successfully, but these errors were encountered: