doc/VariantCallerFunctionalSpecification.rst | 2 1 + 1 - 0 !
1 file changed, 1 insertion(+), 1 deletion(-)

 fix spelling error

Makefile | 4 2 + 2 - 0 !
1 file changed, 2 insertions(+), 2 deletions(-)

 make tests run verbosely
 The cram tests in particular don't output anything until the suite is
 finished. On slower buildd's, this might make the build time-out due to
 apparent lack of activity and report FTBFS.

Makefile | 4 2 + 2 - 0 !
1 file changed, 2 insertions(+), 2 deletions(-)

 disable tests for arrow
 These tests need ConsensusCore2, and the version currently packaged in
 Debian is newer than this GenomicConsensus version and not compatible.
 The tests are thus expected to fail in this situation.

tests/cram/poa-all4mer.t | 1 1 + 0 - 0 !
1 file changed, 1 insertion(+)

 don't use poa convenience script in test suite
 We can't install that convenience script because it conflicts with another
 package, so change the test suite to use `variantCaller --algorithm=poa`
 instead.

Makefile | 9 8 + 1 - 0 !
1 file changed, 8 insertions(+), 1 deletion(-)

 test requires https://github.com/pacificbiosciences/pacbiotestdata which is not packaged
Bug-Debian: https://bugs.debian.org/925909

Makefile | 15 13 + 2 - 0 !
1 file changed, 13 insertions(+), 2 deletions(-)

 ignore tests that are based on non-existing input data that probably reside on upstreams local host
Bug-Debian: https://bugs.debian.org/925909

tests/cram/extra/plurality-fluidigm.t | 3 2 + 1 - 0 !
tests/cram/plurality-compressed.t | 3 2 + 1 - 0 !
tests/cram/quiver-noqvs-test.t | 3 2 + 1 - 0 !
tests/cram/reference-mismatch.t | 8 3 + 5 - 0 !
4 files changed, 9 insertions(+), 8 deletions(-)

 ignore some warnings which are breaking test results
Bug-Debian: https://bugs.debian.org/925909

GenomicConsensus/quiver/model.py | 2 1 + 1 - 0 !
GenomicConsensus/utils.py | 2 1 + 1 - 0 !
tests/unit/AlignmentHitStubs.py | 6 3 + 3 - 0 !
3 files changed, 5 insertions(+), 5 deletions(-)

 fix for
   DeprecationWarning: The binary mode of fromstring is deprecated, as it behaves surprisingly on unicode inputs. Use frombuffer instead
 which despite its only a warning causes test suite errors
Bug-Debian: https://bugs.debian.org/925909