Build error files

[sckott]

@krlmlr This may be something simple I'm missing, but do you know if there is a way to inspect files on errors? For example, this build had an error https://ci.appveyor.com/project/sckott/rnoaa/build/1.0.5#L359 and points to a file, but it's not clear if I can look at this file or not.

[krlmlr]

I don't think artifacts are provided for failed builds, but the .out file in question is actually echoed to the console at line 394ff. by travis-ci. There may be an issue with the ISO image, I'll take a look.

[krlmlr]

This seems to be an issue with running R from an ISO image. See krlmlr/r-portable#8.

[sckott]

@krlmlr I, now I see the output, thanks for pointing that out. We get this same error across a lot of our R packages.

[krlmlr]

This error seems to occurs when running R from a mounted ISO file, and only with R CMD check --as-cran. I'll have to investigate this further.

Currently, there are two options:

• Don't test as CRAN for now, as in this build (https://github.com/krlmlr/r-appveyor/commit/f9434ee0a78e6ab050d468895e84f95ec1a04302)
• Manually install the MASS package (and anything else that's possibly already part of the installation), as in that build (https://github.com/krlmlr/r-appveyor/commit/5f5a4569e107c368bbf11273c222296df7fc4a80)

Every adaptation is just a single line in appveyor.yml, see the SHA1-style links above. The builds haven't run yet, but their success should indicate if the change is likely to work with your package.

[krlmlr]

Both methods -- turning off manual install or not testing as CRAN -- should work.

[sckott]

great, will try, thanks so much

[krlmlr]

I'm applying a rather crude solution here -- copy R from the ISO file to the hard disk. R is supposed to run correctly from the ISO, but doesn't -- see issue report. Once this is merged, you should be able to check "as CRAN" again.

[sckott]

great, thanks for the fix, even if crude