[Bioc-devel] error in bumphunter unit test
Lor|@Shepherd @end|ng |rom Ro@we||P@rk@org
Tue Apr 2 17:06:36 CEST 2019
The version of R devel being used could be significant. There have been a number of changes in R devel that could be the culprit.
Could be completely unrelated but one such example is the random number generator updates:
Please make sure you are using the most recent R-devel.
The version of packages being utilized on the build system will be the versions listed in the build report page:
You could always do a BiocManager::valid() to test a valid install and if any packages should be updated.
Are you using a bioconductor provided devel docker images? If you are, the devel docker image are updated weekly. You might want to pull the latest version. A locally pull docker image does not update automatically.
Bioconductor Core Team
Roswell Park Cancer Institute
Department of Biostatistics & Bioinformatics
Elm & Carlton Streets
Buffalo, New York 14263
From: Bioc-devel <bioc-devel-bounces using r-project.org> on behalf of Samuela Pollack <spollack using jimmy.harvard.edu>
Sent: Tuesday, April 2, 2019 10:17:57 AM
Subject: [Bioc-devel] error in bumphunter unit test
Our bumphunter package is failing its unit tests fairly spectacularly:
the pval algorithm seems to be returning a data frame full of zeroes.
Unfortunately, I have not been able to reproduce this behavior. I have
instantiated an EC2 instance with the devel AMI, updated all the
packages, installed bumphunter and its dependencies, and run the unit
tests without errors.
My sessionInfo indicates all R dependencies are identical to the
snapshot on the devel build report. However, two things may be causing
the disparity in results:
(i) bumphunter uses 'doParallel' and 'foreach' at the point that it is
failing; is it possible for me to confirm that I am using the same
version of these as the build system used. (Note: we are failing even
when doParallel defaults to sequential execution, so the low-level
interface does not seem to be relevant.)
(ii) The devel AMI is running R 3.6 release 75543 and the build system
is running release 76205. Could this be the discrepancy we're looking
for? We are reluctant to reinstall all of R+Bioc unless it looks relevant.
Any other suggestions would be very helpful. We haven't touched the
package in months and are totally buffaloed why it has decided to fail
just days before the new release.
thanks in advance for any advice you can offer,
Bioc-devel using r-project.org mailing list
This email message may contain legally privileged and/or confidential information. If you are not the intended recipient(s), or the employee or agent responsible for the delivery of this message to the intended recipient(s), you are hereby notified that any disclosure, copying, distribution, or use of this email message is prohibited. If you have received this message in error, please notify the sender immediately by e-mail and delete this email message from your computer. Thank you.
[[alternative HTML version deleted]]
More information about the Bioc-devel