gatk-3.8

gatk3的最后一个经典版本3.8

Go to file

Mark DePristo 3164c8dee5 S3 upload now directly creates the XML report in memory and puts that in S3 -- This is a partial fix for the problem with uploading S3 logs reported by Mauricio. There the problem is that the java.io.tmpdir is not accessible (network just hangs). Because of that the s3 upload fails because the underlying system uses tmpdir for caching, etc. As far as I can tell there's no way around this bug -- you cannot overload the java.io.tmpdir programmatically and even if I could what value would we use? The only solution seems to me is to detect that tmpdir is hanging (how?!) and fail with a meaningful error.		2012-01-29 15:14:58 -05:00
public	S3 upload now directly creates the XML report in memory and puts that in S3	2012-01-29 15:14:58 -05:00
settings	Rev. tribble to fix BED codec bug in tribble 51	2012-01-17 16:40:26 -05:00
.gitignore	Minor additions to the shared .gitignore file, now that Mark has checked one in.	2011-10-26 12:24:28 -04:00
LICENSE	One last test...	2011-06-28 19:18:17 -04:00
build.xml	Merged bug fix from Stable into Unstable	2012-01-24 15:19:29 -05:00
ivy.xml	S3 upload now directly creates the XML report in memory and puts that in S3	2012-01-29 15:14:58 -05:00