Skip to content
Prev 8476 / 12125 Next

[R-pkg-devel] debian - how to replicate the error

On Tue, 20 Sep 2022 03:28:09 +0000
"Zhang, Xueqiong" <joan.zhang at emory.edu> wrote:

            
There are Debian builds for both x86_64 and arm64, so it should be
possible to set up a virtual machine on your Mac that would be
relatively quick thanks to hardware virtualisation. For example, you
could start with a Dockerfile for an R-hub builder [1], add the missing
Bioconductor packages and try to reproduce the error there.

This way lies a lot of work, though. Worst case scenario, after you're
done setting up the virtual machine, the test may pass.
Doesn't look likely to me. True, you could use file.path(tempdir(),
'outputs') instead of paste0(...), but that shouldn't cause any
differences between two POSIX-compatible systems that both use a
forward slash as a directory separator.

An error due to file paths would look like "file not found", or tests
for file paths being equivalent failing due to a spurious slash or
something. Your error looks different:
Try instrumenting your tests to produce more output around that line?
(Not sure how to do that with testthat.) Since we don't see the code,
we can't say much else. Where does that data.frame come from? What
could be the reasons for it to miss an "id" column? Does seq_num exist
there too?
No, that's not the problem. POSIX allows an operating system to treat a
double slash in the beginning of a path specially, but on Linux,
multiple slashes anywhere are equivalent to a single slash:

cd ////////usr///////bin && pwd
# /usr/bin