[R-pkg-devel] Win-builder R-devel doesn't appear to be running examples
||gge@ @end|ng |rom @t@t|@t|k@tu-dortmund@de
Thu Jun 17 09:24:53 CEST 2021
Ah! Now I understand the question.
Yes, indeed, when not doing multiarch checks, the location of the files
is a different one and hence they are not copied corectly to the web
space as that part of my script still assumes multiarch check.
I'll try to fix this during the day, so please simply try again tomorrow.
On 16.06.2021 20:03, Kai Aragaki wrote:
> Thank you both. My concern then is with the lack of output in the
> examples and tests directory - where before there was (for each arch) a
> pdf output of an image generated by an example (the output of the
> example was a ggplot) as well as the timings for each example, the
> directory for r-devel is completely empty (not even one arch folder). Is
> this cause for concern?
> Thank you again -
> *From:* Uwe Ligges <ligges using statistik.tu-dortmund.de>
> *Sent:* Wednesday, June 16, 2021 08:16 AM
> *To:* Duncan Murdoch <murdoch.duncan using gmail.com>; Kai Aragaki
> <aaragak1 using jhmi.edu>; r-package-devel using r-project.org
> <r-package-devel using r-project.org>
> *Subject:* Re: [R-pkg-devel] Win-builder R-devel doesn't appear to be
> running examples
> External Email - Use Caution
> Reason is that we currently plan not to support 32-bit Windows as of
> R-4.2.0, i.e. we stopped to build and check for 32-bit Windows in R-devel.
> Uwe Ligges
> Am 16.06.2021 um 13:31 schrieb Duncan Murdoch:
>> On 15/06/2021 5:29 p.m., Kai Aragaki wrote:
>>> Hello all -
>>> I've been testing my package using win-builder, both R-current and
>>> R-devel. Both run with no notes, warnings, or errors aside for it
>>> being a new submission and for false-positive spelling errors.
>>> However, for R-devel, the build log does not show
>>> * loading checks for arch 'i386'
>>> and all its associated logging (the same for x64 - it does not appear)
>>> As such, the examples_and_tests folder is empty, whereas in R-current
>>> it is not.
>>> Is this expected behavior? If not, what are some possible causes of
>>> this issue?
>> You only get that message if "multiarch" tests are requested. If CRAN
>> is running with --no-multiarch it won't show up.
>> Duncan Murdoch
>> R-package-devel using r-project.org mailing list
More information about the R-package-devel