[R-pkg-devel] R package check stuck on “checking use of S3 registration …”

Tomas Kalibera tom@@@k@||ber@ @end|ng |rom gm@||@com
Fri Feb 12 10:39:55 CET 2021


On 2/11/21 8:28 AM, Evan Biederstedt wrote:
> Hi there
>
> Creating an R package here which I plan to upload to CRAN. Upon checking
> the tarball created with `R CMD BUILD`, I try to use `R CMD CHECK` as
> follows:
>
> ```
> R CMD CHECK my_package.tar.gz --as-cran
> ```
>
> This normally works smoothly. However, in this case, it is stuck on
> `checking use of S3 registration` and has been there for several hours.
> I've never experienced this before; here's the partial output I see:
>
>
> ```
> ...
>   * checking package subdirectories ... OK
>   * checking R files for non-ASCII characters ... OK
>   * checking R files for syntax errors ... OK
>   * checking whether the package can be loaded ... OK
>   * checking whether the package can be loaded with stated dependencies ...
> OK
>   * checking whether the package can be unloaded cleanly ... OK
>   * checking whether the namespace can be loaded with stated dependencies
> ... OK
>   * checking whether the namespace can be unloaded cleanly ... OK
>   * checking use of S3 registration ...
>   ```
>
> (1) What does `checking use of S3 registration` really mean?
Reporting when S3 methods in base/recommended packages are overwritten 
by the checked package. These things are documented in R Internals 
manual, search for _R_CHECK_OVERWRITE_REGISTERED_S3_METHODS_. In the 
source code 
(https://svn.r-project.org/R/trunk/src/library/tools/R/check.R) look for 
the same variable or "use of S3 registration".
> (2) More importantly, why could it be stuck here? How could I fix this
> issue?

In principle, you could check if your package is doing something special 
re S3 methods registration and experiment with that to see when the 
problem disappears. Or you could debug on the R end (build R with debug 
symbols, run the example, connect to R via gdb, print the stacktrace, 
etc, etc.). Or create a minimal reproducible example so that someone 
else could do that, instead. In either case, it would be interesting to 
know the cause to see if the checking could be made more robust.

Best
Tomas

> Any insight or help greatly appreciated. Thanks!
>
> 	[[alternative HTML version deleted]]
>
> ______________________________________________
> R-package-devel using r-project.org mailing list
> https://stat.ethz.ch/mailman/listinfo/r-package-devel



More information about the R-package-devel mailing list