Dear Bioconductor developers, I am currently in the review-phase for our package DepecheR (first time). As neither me or the other developer use Windows, we have not run the tests on any Windows operative system before. Now when we do on the automatic single-package builder, it turns out that the tests take approximately three times as long time to run on Windows compared to Ubuntu or Darwin. This means that we get a run-time warning for Windows, which is the final warning that we get. Now, I simply wonder: is this a familiar issue and if so, is there a reasonable simple workaround? It might be worth mentioning that we use quite a lot of foreach-based parallel processing in the package. Very thankful for any input! Best regards Jakob Theorell, MD/PhD Autoimmune Neurology Group Nuffield Department of Clinical Neurosciences University of Oxford
[Bioc-devel] Regarding a discrepancy in test_that speed between Windows and Linux
2 messages · Jakob Theorell, Shepherd, Lori
2 days later
For consistency, the discussion has been moved to the submission. Please see https://github.com/Bioconductor/Contributions/issues/972#issuecomment-456839247 To follow the discussion if interested. Lori Shepherd Bioconductor Core Team Roswell Park Cancer Institute Department of Biostatistics & Bioinformatics Elm & Carlton Streets Buffalo, New York 14263
From: Bioc-devel <bioc-devel-bounces at r-project.org> on behalf of Jakob Theorell <jakob.theorell at ndcn.ox.ac.uk>
Sent: Monday, January 21, 2019 4:31:32 PM
To: bioc-devel at r-project.org
Subject: [Bioc-devel] Regarding a discrepancy in test_that speed between Windows and Linux
Sent: Monday, January 21, 2019 4:31:32 PM
To: bioc-devel at r-project.org
Subject: [Bioc-devel] Regarding a discrepancy in test_that speed between Windows and Linux
Dear Bioconductor developers,
I am currently in the review-phase for our package DepecheR (first time). As neither me or the other developer use Windows, we have not run the tests on any Windows operative system before. Now when we do on the automatic single-package builder, it turns out that the tests take approximately three times as long time to run on Windows compared to Ubuntu or Darwin. This means that we get a run-time warning for Windows, which is the final warning that we get. Now, I simply wonder: is this a familiar issue and if so, is there a reasonable simple workaround? It might be worth mentioning that we use quite a lot of foreach-based parallel processing in the package.
Very thankful for any input!
Best regards
Jakob Theorell, MD/PhD
Autoimmune Neurology Group
Nuffield Department of Clinical Neurosciences
University of Oxford
[[alternative HTML version deleted]]
_______________________________________________
Bioc-devel at r-project.org mailing list
https://stat.ethz.ch/mailman/listinfo/bioc-devel
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.