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

Jenkins problems #335

Closed
cseed opened this issue Apr 22, 2016 · 4 comments
Closed

Jenkins problems #335

cseed opened this issue Apr 22, 2016 · 4 comments

Comments

@cseed
Copy link
Collaborator

cseed commented Apr 22, 2016

Three things:

  1. Jenkins build can't write annotations #116:

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.

  1. I tried to rebuild can't write annotations #116 by clicking "Rebuild" on the left hand side menu. This resulted in build Tp exportmore #119

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?

  1. When I noticed can't write annotations #116 failed, I wanted to find the last build of origin/master that succeeded. Is there a way to do that?
@jigold
Copy link
Collaborator

jigold commented Apr 25, 2016

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.

@tpoterba
Copy link
Contributor

heh, careful with '#' on github

@jigold
Copy link
Collaborator

jigold commented Apr 28, 2016

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:
-Dhail.seed=5
-Dhail.randomize=true

@cseed
Copy link
Collaborator Author

cseed commented Jul 26, 2016

All of these have been resolved.

@cseed cseed closed this as completed Jul 26, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants