David Kane <David Kane
2001-Nov-13 18:02 UTC
[Rd] modification time warning with R CMD check
I often get warnings like the following when running R CMD check [...] * checking for code/documentation mismatches ... OK * checking tests ... make: *** Warning: File `Makevars' has modification time in the future (2001-11-13 12:54:37.381546042 > 2001-11-13 12:54:37.314975985) [...] I am ready to believe that this is not a bug (i.e., that the timing on my various machines and file systems is such that I am creating a Makevars with a modification that is 0.07 seconds in the future from the perspective of the machine that Perl is running on). However, I would think that a warning would only be justified if this were far enough (1 second? 5 seconds?) in the future to be "interesting". I am running 1.3.1 on Solaris mica|tmp> R --version R 1.3.1 (2001-08-31). Copyright (C) 2001 R Development Core Team R is free software and comes with ABSOLUTELY NO WARRANTY. You are welcome to redistribute it under the terms of the GNU General Public License. For more information about these matters, see http://www.gnu.org/copyleft/gpl.html. Thanks, Dave Kane -- David Kane Geode Capital Management 617-563-0122 david.d.kane@fmr.com -.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.- r-devel mailing list -- Read http://www.ci.tuwien.ac.at/~hornik/R/R-FAQ.html Send "info", "help", or "[un]subscribe" (in the "body", not the subject !) To: r-devel-request@stat.math.ethz.ch _._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._
On Tue, 13 Nov 2001, David Kane <David Kane wrote:> I often get warnings like the following when running R CMD check > > [...] > * checking for code/documentation mismatches ... OK > * checking tests ... > make: *** Warning: File `Makevars' has modification time in the future (2001-11-13 12:54:37.381546042 > 2001-11-13 12:54:37.314975985) > [...] > > I am ready to believe that this is not a bug (i.e., that the timing on my > various machines and file systems is such that I am creating a Makevars with a > modification that is 0.07 seconds in the future from the perspective of the > machine that Perl is running on). However, I would think that a > warning would only be justified if this were far enough (1 second? 5 seconds?) > in the future to be "interesting".I get this too from time to time. It's actually hard to tell what is 'uninteresting' in general. For example, Linux can create a file in about 50 microseconds on suitable hardware, so a 0.07s lag is easily enough that files might in principle have been created in the wrong order, messing up the make algorithm. Fortunately in building R this sort of lag doesn't matter. Unfortunately I don't know how to turn the warning off. -thomas -.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.- r-devel mailing list -- Read http://www.ci.tuwien.ac.at/~hornik/R/R-FAQ.html Send "info", "help", or "[un]subscribe" (in the "body", not the subject !) To: r-devel-request@stat.math.ethz.ch _._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._
Seemingly Similar Threads
- FW: Summary of Suggestions for poor man's parallel processing
- R CMD check fails if Depends field includes a package with a `.' in it (PR#1591)
- How to get R cmd to check Fortran array bounds
- (PR#1577) is.na<- coerces character vectors to be factors
- Warning from R CMD build