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

[ADAM-1573] Remove unused Unaligned trait. #1574

Merged

Conversation

@fnothaft
Copy link
Member

@fnothaft fnothaft commented Jun 21, 2017

Resolves #1573.

@fnothaft fnothaft added this to the 0.23.0 milestone Jun 21, 2017
@AmplabJenkins
Copy link

@AmplabJenkins AmplabJenkins commented Jun 21, 2017

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/ADAM-prb/2108/

Build result: FAILURE

[...truncated 15 lines...] > /home/jenkins/git2/bin/git fetch --tags --progress https://github.com/bigdatagenomics/adam.git +refs/pull/:refs/remotes/origin/pr/ # timeout=15 > /home/jenkins/git2/bin/git rev-parse origin/pr/1574/merge^{commit} # timeout=10 > /home/jenkins/git2/bin/git branch -a -v --no-abbrev --contains 1299738 # timeout=10Checking out Revision 1299738 (origin/pr/1574/merge) > /home/jenkins/git2/bin/git config core.sparsecheckout # timeout=10 > /home/jenkins/git2/bin/git checkout -f 1299738cd1053fb3546efd5d2069ae9f0e87d006First time build. Skipping changelog.Triggering ADAM-prb ? 2.6.0,2.11,1.6.1,centosTriggering ADAM-prb ? 2.3.0,2.11,2.0.0,centosTriggering ADAM-prb ? 2.6.0,2.11,2.0.0,centosTriggering ADAM-prb ? 2.6.0,2.10,2.0.0,centosTriggering ADAM-prb ? 2.3.0,2.11,1.6.1,centosTriggering ADAM-prb ? 2.6.0,2.10,1.6.1,centosTriggering ADAM-prb ? 2.3.0,2.10,1.6.1,centosTriggering ADAM-prb ? 2.3.0,2.10,2.0.0,centosADAM-prb ? 2.6.0,2.11,1.6.1,centos completed with result FAILUREADAM-prb ? 2.3.0,2.11,2.0.0,centos completed with result FAILUREADAM-prb ? 2.6.0,2.11,2.0.0,centos completed with result FAILUREADAM-prb ? 2.6.0,2.10,2.0.0,centos completed with result FAILUREADAM-prb ? 2.3.0,2.11,1.6.1,centos completed with result FAILUREADAM-prb ? 2.6.0,2.10,1.6.1,centos completed with result FAILUREADAM-prb ? 2.3.0,2.10,1.6.1,centos completed with result FAILUREADAM-prb ? 2.3.0,2.10,2.0.0,centos completed with result FAILURENotifying endpoint 'HTTP:https://webhooks.gitter.im/e/ac8bb6e9f53357bc8aa8'
Test FAILed.

@fnothaft
Copy link
Member Author

@fnothaft fnothaft commented Jun 21, 2017

@shaneknapp it looks like our build is getting SIGKILLed on @AmplabJenkins. Thoughts?

@heuermh
Copy link
Member

@heuermh heuermh commented Jun 21, 2017

Jenkins, retest this please

@coveralls
Copy link

@coveralls coveralls commented Jun 21, 2017

Coverage Status

Coverage increased (+0.04%) to 83.387% when pulling 2e7953f on fnothaft:issues/1573-remove-unaligned into 152a8ad on bigdatagenomics:master.

@AmplabJenkins
Copy link

@AmplabJenkins AmplabJenkins commented Jun 21, 2017

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/ADAM-prb/2110/
Test PASSed.

@heuermh heuermh merged commit 310d9f9 into bigdatagenomics:master Jun 21, 2017
3 checks passed
3 checks passed
codacy/pr Good work! A positive pull request.
Details
coverage/coveralls Coverage increased (+0.04%) to 83.387%
Details
@AmplabJenkins
default Merged build finished.
Details
@heuermh
Copy link
Member

@heuermh heuermh commented Jun 21, 2017

Thank you, @fnothaft

@shaneknapp
Copy link
Contributor

@shaneknapp shaneknapp commented Jun 21, 2017

@shaneknapp
Copy link
Contributor

@shaneknapp shaneknapp commented Jun 21, 2017

wow. i literally have no idea what happened. the builds that were SIGKILLED were spread over a few different workers, there's nothing in any of the system or jenkins logs and dmesg looks fine.

and now things are building fine.

nothing to see here, please move along! everything is fine!
fine

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

Successfully merging this pull request may close these issues.

None yet

5 participants