the disk backed queue should set "canAdd" to false whenever we have #376
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
spilled to disk and have started removing records from RAM, or whenever
we start removing records from disk. The pathology was that we would
let callers add if there was any room in ram, regardless if we had
spilled records to disk, thus causing records to become out of order.
If the entire queue is empty, we set canAdd to true again. Added test
to make sure an exception is thrown if we add when we should not.
See: broadinstitute/picard#327
@bradtaylor