Closed ldmax closed 8 months ago
This seems to be coming from the devtools test suite, which is in the devtools repo, so I am transferring this issue there.
This seems to be coming from the devtools test suite, which is in the devtools repo, so I am transferring this issue there.
Yes this is regarding devtools test suite.
Thanks gaborcsardi!
I'm not fixing this right now but did some research. These are notes for when I come back.
This set of tests:
should presumably be testing against a fixture package, not devtools itself.
Also seems like there should be a call to withr::local_temp_libpaths()
.
Dear author,
Our team installed devtools from a snapshot of 2022-08-24. devtools is installed in a central package repository along with other R packages. In order to keep reproducibility or "harmony" of all packages in the repository, all packages should come from the same snapshot.
However, when running tests of devtools, I found it downloading packages AS DEPENDENCIES out of that snapshot. These downloaded packages are of different versions compared to those in the snapshot and polluted the package repository.
Part of log of running tests:
You can see that for dependency rlang, it's installed using https://cloud.r-project.org/src/contrib/rlang_1.0.6.tar.gz, which is version 1.0.6. While in snapshot 2022-08-24, the version is 1.0.4:
Since this dependency rlang is installed under the same path of devtools, it silently replaced previously installed rlang version 1.0.4. There are other dependency packages of devtools installed and silently replace previously installed packages. Thus our package repository gets polluted.
Would it be possible to have dependency packages in your test, that also come from the same snapshot you publish devtools itself? That is, if you publish devtools to snapshot 2022-08-24, dependency packages should also come from the same snapshot.
Many thanks for your time!