Skip to content

[R-pkg-devel] Date of CRAN checks

4 messages · Simon Urbanek, Lluís Revilla, Uwe Ligges

Original
Lluís Revilla
# 
Dear list,

Recently after a package update I noticed an ERROR on one flavor.
I believe this is some problem with the r-release-macos-x86_64 flavor.
But I'm not sure if this is fixed on the system or not.
I was waiting to see if this got fixed with time (and thanks to the CRAN
volunteers).

A check landing page on CRAN had a date "Last updated on 2025-01-29
08:49:42 CET." then it changed to "2025-01-29 15:49:25 CET.". Because there
are some checks that are still from the old version of the package and the
failing check is still failing, I'm not sure which checks were updated. Is
this the date of the landing page of all the checks, or all the checks are
updated up to that date?

Bioconductor provides the time with two fields: StartedAt and EndedAt for
each flavor (and step).
I hoped to find a date on the check logs. It would make it easier to know
when it is updated and it has the same result as previously.
Is there a way to know when a given check was run on CRAN?

Best regards,

Llu?s

PS:  The problem is shared by many packages (>50), the vignette can be
built but not rebuilt and it raises an error message about not finding
pandoc.
Simon Urbanek
# 
Llu?s,

the timestamps are generated by the CRAN server when it updates webpage from the actual check reports so it does not reflect the date/time of the check itself (neither does the timestamp of the URL as it is often re-generated). So in short, no, there is no way to know the timestamp of the check. I think it may be useful, so I'll see if we can add it.

That said, checks are not re-run unless you update the version of your package (or there is an error caused by another package whose update will fix it), so in most cases waiting won't fix anything. If there is a problem you have to report it to the corresponding CRAN maintainer so for macOS that would be me.

Cheers,
Simon
Lluís Revilla
# 
Dear Simon,

Thank you for clearing my misunderstanding about CRAN's checks.
Looking forward to seeing logs with a date (if possible).

This case  was initiated by teal.reporter, the error is related to pandoc
according to the logs:
Error: pandoc version 1.12.3 or higher is required and was not found (see
the help page ?rmarkdown::pandoc_available). Execution halted
The package imports rmarkdown (? 2.23) that requires pandoc.
In teal.reporter there isn't a specific requirement for pandoc version
1.12.3 (but it doesn't check the version available).

Other packages on that same flavor fail with problems related to pandoc,
for example datacutr, oldr or linevis, have similar errors.
They depend on packages that use pandoc and are also recently published.

Many thanks for your help,

Llu?s

On Wed, 29 Jan 2025 at 20:08, Simon Urbanek <simon.urbanek at r-project.org>
wrote:

  
  


  


      

    

    
1 day later

    

      
      

        


  

        

      Uwe Ligges
    

    

      
      #
    

  


  

      
On 29.01.2025 20:08, Simon Urbanek wrote:

            

      
      
      
    

        
That is true for Mac flavours. All others get regularly updated 
(R-devel), or at least if any dependency in the hierarchy is updated 
(Windows R-release/oldrelease).

Best,
Uwe Ligges


 > unless you update the version of your package (or there is an error 
caused by another package whose update will fix it), so in most cases 
waiting won't fix anything. If there is a problem you have to report it 
to the corresponding CRAN maintainer so for macOS that would be me.>