Checkpoint.txt file in Alignment directories is not parsed correctly #96
Labels
bug
Something isn't working
Milestone
Comments
ressy
added a commit
that referenced
this issue
Aug 27, 2020
The example files here cover all three cases I've observed in Checkpoint.txt files, two of which would not parse correctly with the existing load_checkpoint code. These tests assume we get back a 2-member list with an integer and a keyword in all three cases.
ressy
added a commit
that referenced
this issue
Aug 27, 2020
Switch from a single integer to a list containing an integer+keyword pair
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Related to #91,
illumina.util.load_checkpointonly works as expected with the most common case, for a completed FASTQGeneration. Looking at Checkpoint.txt for interrupted/failed cases I see that in general there's both an integer and a keyword (which just happens to be an empty string in the common case).load_checkpointshould be updated to parse out both an integer and a keyword in all cases.The text was updated successfully, but these errors were encountered: