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

Added test to try and repro #1282. #1292

Conversation

@fnothaft
Copy link
Member

fnothaft commented Nov 26, 2016

@heuermh I couldn't reproduce the hang you were seeing in #1282. Any thoughts as to a test to reproduce the hang? Perhaps we diagnosed the hang wrong?

@AmplabJenkins
Copy link

AmplabJenkins commented Nov 26, 2016

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

@heuermh
Copy link
Member

heuermh commented Nov 28, 2016

From the jenkins test failure linked in the original issue above

Build timed out (after 45 minutes). Marking the build as aborted.
Build was aborted
Recording test results
Publishing Scoverage XML and HTML report...
2016-11-16 16:28:18 ERROR Executor:95 - Exception in task 0.0 in stage 2.0 (TID 2)
java.lang.RuntimeException: Piped command List(tee, /dev/null) exited with error code 143.
	at org.bdgenomics.adam.rdd.GenomicRDD$$anonfun$12.apply(GenomicRDD.scala:297)
	at org.bdgenomics.adam.rdd.GenomicRDD$$anonfun$12.apply(GenomicRDD.scala:254)
	at org.apache.spark.rdd.RDD$$anonfun$mapPartitions$1$$anonfun$apply$20.apply(RDD.scala:710)
...
- don't lose any variants when piping as VCF *** FAILED ***
  org.apache.spark.SparkException: Job aborted due to stage failure: Task 0 in stage 2.0
failed 1 times, most recent failure: Lost task 0.0 in stage 2.0 (TID 2, localhost):
java.lang.RuntimeException: Piped command List(tee, /dev/null) exited with error code 143.

Is the error code 143 from tee being sent a kill/interrupt from the Jenkins test runner?

I was thinking the actual error causing the problem was an invalid VCF stream being read back in via VCFInFormatter, which threw an exception or something and then couldn't close the streams in the external process.

@fnothaft
Copy link
Member Author

fnothaft commented Mar 3, 2017

Closing as out of date.

@fnothaft fnothaft closed this Mar 3, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked issues

Successfully merging this pull request may close these issues.

None yet

3 participants
You can’t perform that action at this time.