diagnosing a CMD check failure

I have created a quite minimal package with a simple R program in the
tests subfolder.

When I run CMD check, I get

* checking examples ... OK
* checking for unstated dependencies in tests ... OK
* checking tests ...sh: : No such file or directory
  ERROR

I don't see a way of diagnosing this.  The content of tests is the program t1.R

rex-bash-3.2$ cat t1.R
date()

On other machines I can successfully check the package, so it must be
a problem with my particular
configuration but how can I track down the problem?

 sessionInfo()

R version 2.13.0 Under development (unstable) (2010-11-11 r53555)
Platform: x86_64-unknown-linux-gnu (64-bit)

locale:
[1] C

attached base packages:
[1] stats     graphics  grDevices datasets  utils     methods   base

system("date")

system2("date")

On 17/12/2010 2:12 PM, Vincent Carey wrote:

I have created a quite minimal package with a simple R program in the
tests subfolder.

When I run CMD check, I get

* checking examples ... OK
* checking for unstated dependencies in tests ... OK
* checking tests ...sh: : No such file or directory
?ERROR

I don't see a way of diagnosing this. ?The content of tests is the program
t1.R

rex-bash-3.2$ cat t1.R
date()

On other machines I can successfully check the package, so it must be
a problem with my particular
configuration but how can I track down the problem?

Try running tools::.check_packages directly. ?The problem is coming in the
local function run_tests.

Duncan Murdoch

?sessionInfo()

R version 2.13.0 Under development (unstable) (2010-11-11 r53555)
Platform: x86_64-unknown-linux-gnu (64-bit)

locale:
[1] C

attached base packages:
[1] stats ? ? graphics ?grDevices datasets ?utils ? ? methods ? base