Closed zkamvar closed 3 years ago
N.B. I realized that I never tested bitwise.ia()
on Windows because the NOT_CRAN
was never assigned on Appveyor and so those tests were never run. Luckily, this one test with bitwise.ia()
is the only one that fails. Here are the results after I comment out the not_cran()
from bitwise.ia()
tests:
== Warnings ====================================================================
-- Warning (test-values.R:345:3): bitwise.ia can handle large samples ----------
An integer overflow has occured and the resulting index will not be accurate.
Please consider using a smaller sample.
Backtrace:
1. poppr::bitwise.ia(x[, snps], thread = 1L) test-values.R:345:2
== Failed tests ================================================================
-- Failure (test-values.R:346:3): bitwise.ia can handle large samples ----------
`res` not equal to 8.6296328853274e-06.
1/1 mismatches
[1] -2.21 - 8.63e-06 == -2.21
[ FAIL 1 | WARN 1 | SKIP 182 | PASS 376 ]
It appears that bitwise.ia() is not performing well on Windows as it seems to overflow the stack too early. This test in particular fails on both windows flavors:
https://github.com/grunwaldlab/poppr/blob/0ab416f30c78f08fe23fe7a079b1900449a54e94/tests/testthat/test-values.R#L340-L347
here's the error summary:
R CMD check output on winbuilder
``` * using log directory 'd:/RCompile/CRANguest/R-release/poppr.Rcheck' * using R version 4.0.3 (2020-10-10) * using platform: x86_64-w64-mingw32 (64-bit) * using session charset: ISO8859-1 * checking for file 'poppr/DESCRIPTION' ... OK * checking extension type ... Package * this is package 'poppr' version '2.8.7' * package encoding: UTF-8 * checking CRAN incoming feasibility ... WARNING Maintainer: 'Zhian N. Kamvar