With R-devel compiled with clang-10, strict barrier and gctorture too (see CRAN_Release.cmd for commands). Hasn't finished yet, but this is output so far is below.
The 1036.* fails probably are knock-on effects from the first 1036.02.
Unlikely to be a memory fault related to gctorture. More likely some extra strict checks turned on when strict barrier is on too, possibly new in latest R-devel.
> print(Sys.time()); started.at<-proc.time(); try(test.data.table()); print(Sys.time()); print(timetaken(started.at))
[1] "2020-07-21 00:39:28.074113 MDT"
getDTthreads(verbose=TRUE):
This installation of data.table has not been compiled with OpenMP support.
omp_get_num_procs() 1
R_DATATABLE_NUM_PROCS_PERCENT unset (default 50)
R_DATATABLE_NUM_THREADS unset
R_DATATABLE_THROTTLE unset (default 1024)
omp_get_thread_limit() 1
omp_get_max_threads() 1
OMP_THREAD_LIMIT unset
OMP_NUM_THREADS unset
RestoreAfterFork true
data.table is using 1 threads with throttle==1024. See ?setDTthreads.
test.data.table() running: /home/mdowle/build/R-devel-strict-clang/library/data.table/tests/tests.Rraw
Running test id 1036.02 Test 1036.02 didn't produce the correct warning :
Expected: All measure variables not of type 'character' will be coerced
Observed: type 31 is unimplemented in 'type2char'
Test 1036.02 produced 1 errors but expected 0
Expected:
Observed: CAR/CDR/TAG or similar applied to unknown type #31 object
Running test id 1036.03 Test 1036.03 ran without errors but failed check that x equals y:
> x = length(levels(ans$variable))
First 1 of 1 (type 'integer'):
[1] 100
> y = 317L
First 1 of 1 (type 'integer'):
[1] 317
Mean relative difference: 2.17
Running test id 1036.04 Test 1036.04 ran without errors but failed check that x equals y:
> x = levels(ans$variable)[c(1, 2, 316, 317)]
First 4 of 4 (type 'character'):
[1] "V1" "V2" NA NA
> y = tt <- c("Geography", "Estimate; SEX AND AGE - Total population", "Percent; HISPANIC OR LATINO AND RACE - Total housing units", "Percent Margin of Error; HISPANIC OR LATINO AND RACE - Total housing units")
First 4 of 4 (type 'character'):
[1] "Geography"
[2] "Estimate; SEX AND AGE - Total population"
[3] "Percent; HISPANIC OR LATINO AND RACE - Total housing units"
[4] "Percent Margin of Error; HISPANIC OR LATINO AND RACE - Total housing units"
'is.NA' value mismatch: 0 in current 2 in target
Running test id 1036.05 Test 1036.05 ran without errors but failed check that x equals y:
> x = range(as.integer(ans$variable))
First 2 of 2 (type 'integer'):
[1] 1 100
> y = INT(1, 317)
First 2 of 2 (type 'integer'):
[1] 1 317
Mean relative difference: 2.17
Running test id 1036.06 Test 1036.06 ran without errors but failed check that x equals y:
> x = as.vector(table(table(as.integer(ans$variable))))
First 1 of 1 (type 'integer'):
[1] 100
> y = INT(309, 8)
First 2 of 2 (type 'integer'):
[1] 309 8
Numeric: lengths (1, 2) differ
Running test id 1036.07 Test 1036.07 ran without errors but failed check that x equals y:
> x = sapply(ans, class)
First 2 of 2 (type 'character'):
variable value
"factor" "integer"
> y = c(Id = "character", Id2 = "integer", variable = "factor", value = "character")
First 4 of 4 (type 'character'):
Id Id2 variable value
"character" "integer" "factor" "character"
Names: 2 string mismatches
Lengths (2, 4) differ (string compare on first 2)
1 string mismatch
Running test id 1372.26
... still running
Update: The errors above in test 1036 were fixed in #4631 before release. I left this extra strict test running and I did not hold up release to CRAN. It progressed to about test 1800 with no more problems so I let the CRAN release go ahead owing to the pressing nature of the release; e.g. data.table error status preventing R-core team from seeing the impact of their changes to R-devel. It has finished now and there was one more problem: test 2127.
Running test id 1729.08 Skipped test 1729.9 due to capabilities()["long.double"] == FALSE
Running test id 1759 Test 1760 not run because this session either has no OpenMP or has been limited to one thread (e.g. under UBSAN and ASAN)
Running test id 1830.6 Skipped tests 1830.7 and 1830.8 due to capabilities()["long.double"] == FALSE
Running test id 2127.58 Test 2127.58 produced 1 errors but expected 0
Expected:
Observed: Argument #6 has different class than argument #2, Please make sure all output values have the same class.
Running test id 2127.59 Test 2127.59 produced 1 errors but expected 0
Expected:
Observed: Argument #6 has different class than argument #2, Please make sure all output values have the same class.
Running test id 2152
Fri Jul 24 03:27:25 2020 endian==little, sizeof(long double)==0, sizeof(pointer)==8, TZ==unset, Sys.timezone()=='America/Denver', Sys.getlocale()=='LC_CTYPE=en_US.UTF-8;LC_NUMERIC=C;LC_TIME=en_US.UTF-8;LC_COLLATE=en_US.UTF-8;LC_MONETARY=en_US.UTF-8;LC_MESSAGES=en_US.UTF-8;LC_PAPER=en_US.UTF-8;LC_NAME=C;LC_ADDRESS=C;LC_TELEPHONE=C;LC_MEASUREMENT=en_US.UTF-8;LC_IDENTIFICATION=C', l10n_info()=='MBCS=TRUE; UTF-8=TRUE; Latin-1=FALSE', getDTthreads()=='This installation of data.table has not been compiled with OpenMP support.; omp_get_num_procs()==1; R_DATATABLE_NUM_PROCS_PERCENT==unset (default 50); R_DATATABLE_NUM_THREADS==unset; R_DATATABLE_THROTTLE==unset (default 1024); omp_get_thread_limit()==1; omp_get_max_threads()==1; OMP_THREAD_LIMIT==unset; OMP_NUM_THREADS==unset; RestoreAfterFork==true; data.table is using 1 threads with throttle==1024. See ?setDTthreads.'
Error in test.data.table() :
8 errors out of 9983. Search tests/tests.Rraw for test numbers: 1036.02, 1036.03, 1036.04, 1036.05, 1036.06, 1036.07, 2127.58, 2127.59.
[1] "2020-07-24 03:27:28.260598 MDT"
[1] "74:47:58 elapsed (74:47:08 cpu)"
With R-devel compiled with clang-10, strict barrier and gctorture too (see CRAN_Release.cmd for commands). Hasn't finished yet, but this is output so far is below.
The 1036.* fails probably are knock-on effects from the first 1036.02.
Unlikely to be a memory fault related to gctorture. More likely some extra strict checks turned on when strict barrier is on too, possibly new in latest R-devel.
Update: The errors above in test 1036 were fixed in #4631 before release. I left this extra strict test running and I did not hold up release to CRAN. It progressed to about test 1800 with no more problems so I let the CRAN release go ahead owing to the pressing nature of the release; e.g. data.table error status preventing R-core team from seeing the impact of their changes to R-devel. It has finished now and there was one more problem: test 2127.