Re: [Bioc-devel] Wishlist: on demand R CMD check

Kasper, correct me if I'm wrong... The way I understand it, Kasper would like a way to test on an *identical* setup such that he can reproduce the issues he sees on the Bioc servers, but that he cannot reproduce elsewhere. I've been there a few times as well and when it happens you end up spendin

Re: [Bioc-devel] Wishlist: on demand R CMD check

Kasper, You can set this up yourself using a combination of Travis-CI (for linux and OSX) and Appveyor (for Windows). The R integration for Travis is now build in, however for Appveyor you will need to use the r-appveyor

Re: [Bioc-devel] Wishlist: on demand R CMD check

I was not envisioning a "proper" check, merely running R CMD check with the current version on the build system of all packages (latest R CMD check). Somehow I imagine we have an R with all of Bioc installed as per a certain check date, although this might not be what is actually happening. So thi

Re: [Bioc-devel] Wishlist: on demand R CMD check

To what extend could the single package builder be used for such a feature? This would not address Michael's point, but it is a way to get access to all archs using existing software infrastructure. Laurent On 2 June 2015 13:18, Michael Lawrence wrote: > Maybe the motion towards github and the

Re: [Bioc-devel] Wishlist: on demand R CMD check

Maybe the motion towards github and the work Gabor C has been doing on Travis integration might help with this? Note that a proper check should test all reverse dependencies of your package, and that would get expensive for some of the more core packages... so that might need to be deferred to the

Re: [Bioc-devel] Wishlist: on demand R CMD check

On Tue, Jun 2, 2015 at 5:32 AM, Vincent Carey wrote: > I agree that this would be nice; not sure how feasible. Could a specific > approach with containers provide a solution? > Unfortunately, containers are linux microkernels, so Windows and MacOS are basically out. > On Mon, Jun 1, 2015 at 1

Re: [Bioc-devel] Wishlist: on demand R CMD check

I agree that this would be nice; not sure how feasible. Could a specific approach with containers provide a solution? On Mon, Jun 1, 2015 at 11:09 PM, Kasper Daniel Hansen < kasperdanielhan...@gmail.com> wrote: > For a substantial number of issues with R CMD check, it is easy to > reproduce the