-
Notifications
You must be signed in to change notification settings - Fork 592
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
Update the large CRAM files to v3.0. #8832
Conversation
Github actions tests reported job failures from actions build 9085418098
|
Github actions tests reported job failures from actions build 9085946968
|
Github actions tests reported job failures from actions build 9368869663
|
final SAMRecordIterator sourceIterator = sourceReader.iterator(); | ||
final SAMRecordIterator targetIterator = copyReader.getIterator(); | ||
|
||
while (sourceIterator.hasNext() && targetIterator.hasNext()) { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You're missing out on the exciting method BaseTest.assertCondition()
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@cmnbroad This looks good to me.
This PR adds a CRAM v3.0 version of the existing (CRAM v2.1) test file
CEUTrio.HiSeq.WGS.b37.NA12878.20.21.cram
in git-lfs and in the cloud test resources bucket. In both cases, the old files are left intact for now. Roundtrip tests using both the old and new versions of the local file are also added.At some point, the old files can be removed, but when we do so, old branches will need to be rebased on this code or the cloud tests will fail, since the cloud test in this PR uses the new file name (that includes the CRAM version in the name).