Opened 20 months ago
Last modified 9 months ago
#67059 assigned defect
R BATCH does not work: BATCH: line 60: 30867 Illegal instruction ${R_HOME}/bin/R -f ${in} ${opts}
Reported by: | barracuda156 | Owned by: | i0ntempest |
---|---|---|---|
Priority: | Normal | Milestone: | |
Component: | ports | Version: | 2.8.1 |
Keywords: | Cc: | ||
Port: | R |
Description
Example:
* checking tests ... Running ‘spelling.R’ Running ‘testthat.R’/opt/local/Library/Frameworks/R.framework/Resources/bin/BATCH: line 60: 30867 Illegal instruction ${R_HOME}/bin/R -f ${in} ${opts} ${R_BATCH_OPTIONS} > ${out} 2>&1 ERROR Running the tests in ‘tests/testthat.R’ failed. Complete output: > library(testthat) > library(usethis) > > test_check("usethis")
(I had another identical case with another package, but cannot remember which one now.)
Any idea what goes wrong?
Change History (6)
comment:1 Changed 20 months ago by barracuda156
comment:2 Changed 20 months ago by barracuda156
Another instance with R-rhdf5filters
:
* checking tests ... Running ‘testthat.R’/opt/local/Library/Frameworks/R.framework/Resources/bin/BATCH: line 60: 63007 Abort trap ${R_HOME}/bin/R -f ${in} ${opts} ${R_BATCH_OPTIONS} > ${out} 2>&1 ERROR Running the tests in ‘tests/testthat.R’ failed.
comment:3 Changed 15 months ago by barracuda156
Looks like another case of broken R BATCH: https://github.com/stla/kantorovich/issues/1#issuecomment-1688911204
comment:4 Changed 13 months ago by barracuda156
It is in fact broken overall in Macports, it seems; just got this on Sonoma:
---> Testing R-literanger * using log directory ‘/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_R_R-literanger/R-literanger/work/literanger-0.0.2/literanger.Rcheck’ * using R version 4.3.1 (2023-06-16) * using platform: aarch64-apple-darwin23.0.0 (64-bit) * R was compiled by clang version 15.0.7 GNU Fortran (MacPorts gcc12 12.3.0_3+stdlib_flag) 12.3.0 * running under: macOS Sonoma 14.0 * using session charset: UTF-8 * checking for file ‘literanger/DESCRIPTION’ ... OK * this is package ‘literanger’ version ‘0.0.2’ * package encoding: UTF-8 * checking package namespace information ... OK * checking package dependencies ...Warning: unable to access index for repository https://CRAN.R-project.org/src/contrib: cannot open URL 'https://CRAN.R-project.org/src/contrib/PACKAGES' OK * checking if this is a source package ... OK * checking if there is a namespace ... OK * checking for executable files ... OK * checking for hidden files and directories ... OK * checking for portable file names ... OK * checking for sufficient/correct file permissions ... OK * checking whether package ‘literanger’ can be installed ... OK * used C++ compiler: ‘clang version 15.0.7’ * used SDK: ‘MacOSX14.0.sdk’ * checking installed package size ... OK * checking package directory ... OK * checking DESCRIPTION meta-information ... OK * checking top-level files ... OK * checking for left-over files ... OK * checking index information ... OK * checking package subdirectories ... OK * checking R files for non-ASCII characters ... OK * checking R files for syntax errors ... OK * checking whether the package can be loaded ... OK * checking whether the package can be loaded with stated dependencies ... OK * checking whether the package can be unloaded cleanly ... OK * checking whether the namespace can be loaded with stated dependencies ... OK * checking whether the namespace can be unloaded cleanly ... OK * checking loading without being on the library search path ... OK * checking dependencies in R code ... OK * checking S3 generic/method consistency ... OK * checking replacement functions ... OK * checking foreign function calls ... OK * checking R code for possible problems ... OK * checking Rd files ... OK * checking Rd metadata ... OK * checking Rd cross-references ... OK * checking for missing documentation entries ... OK * checking for code/documentation mismatches ... OK * checking Rd \usage sections ... OK * checking Rd contents ... OK * checking for unstated dependencies in examples ... OK * checking line endings in C/C++/Fortran sources/headers ... OK * checking line endings in Makefiles ... OK * checking compilation flags in Makevars ... OK * checking for GNU extensions in Makefiles ... OK * checking for portable use of $(BLAS_LIBS) and $(LAPACK_LIBS) ... OK * checking use of PKG_*FLAGS in Makefiles ... OK * checking compiled code ... OK * checking examples ... OK * checking for unstated dependencies in ‘tests’ ... OK * checking tests ... Running ‘testthat.R’/opt/local/Library/Frameworks/R.framework/Resources/bin/BATCH: line 60: 69280 Trace/BPT trap: 5 ${R_HOME}/bin/R -f ${in} ${opts} ${R_BATCH_OPTIONS} > ${out} 2>&1 ERROR Running the tests in ‘tests/testthat.R’ failed. Complete output: > library(testthat) > library(literanger) > > test_check('literanger')
comment:6 Changed 9 months ago by barracuda156
Another issue of the same error: https://github.com/etiennebacher/altdoc/issues/254
Note: See
TracTickets for help on using
tickets.
With another port,
R-milr
, tests simply freeze due to this issue. Control+C interrupts the freeze, and then the log has this BATCH error.