search for: checklog

...summary; it's probably not bullet-proof, but perhaps others will find it useful for packages, like the Rcmdr, that currently generate many notes about global variables: ------------- snip ------------ findGlobals <- function(filein="00check.log", fileout="globals.R"){ checklog <- readLines(filein) whichline <- which(grepl("checking R code for possible problems .* NOTE", checklog)) checklog <- checklog[-(1:whichline)] whichline <- which(grepl("checking Rd files", checklog)) checklog <- checklog[-(whichline:length(checklog))] gl...

...f R on my linux box (Ubuntu 24.04.1 LTS). The last development version that was successfully compiled and installed on my machine is "R Under development (unstable) (2024-12-31 r87500)". Since then the script always fails on one of the regression tests; details are in the attached file R-CheckLog.txt. I also include a file (R-Script.txt) which shows why this test fails on my machine using the last R development version that did install on my machine. It seems the command 'si$LAPACK <- ""' introduces an extra line in the output of 'capture.output(si)' which the...

...exactly what the script does. Then on line 8, the $unique variable is set to a random 6 character wide string, a ''cookie'' of sorts, this is used as a log prefix so that you can see which particular instance of the script does what. Then a couple of functions are initialized. The checklog() and logmsg() functions take care of logging at the requested loglevel (set in xen.conf). This is different from line 4; logmsg is a function that logs to the console, syslog, or a file (xen.conf). The sigerr(), fatal(), success(), xenstore_read_default(), findCommand() and evalVariables() functi...

...exactly what the script does. Then on line 8, the $unique variable is set to a random 6 character wide string, a ''cookie'' of sorts, this is used as a log prefix so that you can see which particular instance of the script does what. Then a couple of functions are initialized. The checklog() and logmsg() functions take care of logging at the requested loglevel (set in xen.conf). This is different from line 4; logmsg is a function that logs to the console, syslog, or a file (xen.conf). The sigerr(), fatal(), success(), xenstore_read_default(), findCommand() and evalVariables() functi...