On 21/07/2017 13:34, Graham Inggs wrote:
The two test_vcf_norm failures are caused by the following differing
output on 32-bit architectures:
The tests were modified here:
https://github.com/samtools/bcftools/commit/e43ca8c70bbc78a4ef29be723c60a2ec7a029436
The difference was introduced here:
https://github.com/samtools/bcftools/commit/25d042b833987d32e5de1fc3a109d357c4d0f738
--- a/vcfnorm.c
+++ b/vcfnorm.c
...
+static inline int has_non_acgtn(char *seq, int nseq)
+{
+ char *end = nseq ? seq + nseq : seq + UINT32_MAX; // arbitrary
large number
...
Changing UINT32_MAX above to (UINT32_MAX >> 2) allows the tests to succeed.
