Dear All,
Before doing something I shouldn't I want to make sure how to proceed:
a few hours ago, a new version of testthat has been made available in CRAN
(v. 1.0.0); this version can be more picky with statements such as
expect_output(out, "some message")
Now (depending on the details, which
The build system will automatically pick up new versions from CRAN when they
are available. So yes, packages (in both release and devel) need to be
compatible with the changes in the new testthat.
Dan
- Original Message -
> From: "Ramon Diaz-Uriarte"
> To: "bioc-devel"
> Cc: "ramon d
Basically (and this is true for release as well) CRAN packages gets pushed
to the build system frequently. I don't know if testthat has been pushed
to the devel build setup yet, but it will happen and you will get a
problem. If not now, then shortly after release.
So I recommend updating, and ad
Thanks for the reply. Updated in the svn repo.
Best,
R.
On Thu, 14-04-2016, at 16:46, Dan Tenenbaum wrote:
> The build system will automatically pick up new versions from CRAN when they
> are available. So yes, packages (in both release and devel) need to be
> compatible with the changes in
On Thu, 14-04-2016, at 16:47, Kasper Daniel Hansen
wrote:
> Basically (and this is true for release as well) CRAN packages gets pushed
> to the build system frequently.
Then, it should be updated; no question :-).
> I don't know if testthat has been pushed to the devel build setup yet,
> but
Indeed, build/check reports were generated now on the moscato2 windows
server as well and the error has disappeared!
Thanks again,
Maarten
On Tue, Apr 12, 2016 at 3:23 PM, Kasper Daniel Hansen <
kasperdanielhan...@gmail.com> wrote:
> Yes. But I agree it is _really_ weird since minfi and illumin
