[Bioc-devel] Package update before october 23rd deadline and build errors [duplicated, wrong email address previous]

[Giulia Pais]

Hi Lori, thanks for your reply, unfortunately the problem persists, same 
as the previous build it appears to have issues with BiocParallel that 
we don't have both on local machines and github actions server machines. 
What should we do? Thank you

Il 21/10/2020 14:33, Kern, Lori ha scritto:
> We are sorry for the inconvenience.� There was an issue generating the 
> build report, again.� We hope to have it resolved and have the new 
> build report posted later today.� I do see the 0.99.13 updates in our 
> git repository so they were pushed up and should be reflected in the 
> next posted build report.
> Please see if the issues clear up on the next build report otherwise 
> we can investigate further if there is an issue with the BiocParallel 
> implementation.
>
> Lori Shepherd
>
> Bioconductor Core Team
>
> Roswell Park Comprehensive Cancer Center
>
> Department of Biostatistics & Bioinformatics
>
> Elm & Carlton Streets
>
> Buffalo, New York 14263
>
> ------------------------------------------------------------------------
> *From:* Bioc-devel <bioc-devel-bounces using r-project.org> on behalf of 
> Giulia Pais <giuliapais1 using gmail.com>
> *Sent:* Wednesday, October 21, 2020 5:58 AM
> *To:* bioc-devel using r-project.org <bioc-devel using r-project.org>
> *Subject:* [Bioc-devel] Package update before october 23rd deadline 
> and build errors [duplicated, wrong email address previous]
> Hello, bioconductor team,
>
> I'm one of the contributors for the package ISAnalytics. We pushed some
> changes we would like to be included in the release for bioconductor
> 3.12 a couple of days ago but the build report still refers to the older
> version, did we miss the deadline for updates or is it normal? Moreover,
> by taking a look at the build report for the older version we noticed it
> had failed on Windows, which is to us very odd, since we develop and
> check the package on windows locally and we also have github automated
> actions that perform the same checks on other machines and there were no
> errors or warnings. From what we can see from the report it seems a
> BiocParallel problem, could you give us feedback on this please? The
> link to the build report:
> http://secure-web.cisco.com/1zHzlluYonVKy4ELoeCYul0uSR_LsrM-vATHafqCNWVC9GInGrIBBBUFD5evQqHGxEq3urvQtUqxFyRWZKHpwbQ8NV_UQoFsgnSGWJn6jay5_Vh89KT0OA7y8PNREUH-tSKNv34NZMyW6TGTUyOX0hHdYvwKx014kLa5Jtq9tcBtUzNwL_kaT94QNsgn2OdTriktDiI_jMdN_FKV4qtbdP1yTM_FG6NtIox4l8sLKzC5oB3cgvTG9dXqbQ-6K1iVRaz2ml_Prw6T0M-3Ye_A6Lck77kjUxwBKVXSc31mH3vpOiR4-PJBKlk8oXUn3Z15v/http%3A%2F%2Fbioconductor.org%2FcheckResults%2Fdevel%2Fbioc-LATEST%2FISAnalytics%2F
>
> Thank you in advance,
>
> Giulia Pais
>
> _______________________________________________
> Bioc-devel using r-project.org mailing list
> https://secure-web.cisco.com/13zn0ely3HlLpozIs-qHy1js8Mi-OmANT3Cl7A72-MML9cpPyjxJp2WMuYvCIwmT7R-hwG_qxD13paKEwm9Obd3l3G7MkGILTmsrp2YiT4Zk4WzRBVh8b8I1WrfneDJ1KQJxsTLoa8h1VsiajJqiwkaZoL5ScfJ7BftT2ZAfBZr-cNAaZPpMwQpO7GS_5jEIFO0dIe7flKrJ1oSg_zf3yxdzwSXUWtddWYSGPwrbB5mU0xzHmVsxiLk2JRvsxf0sCPv8q1MaOJotii9fVcATKGtlKDOryUNYXq52di1RizZHPPzdEdi32oxGSIUwcucgK/https%3A%2F%2Fstat.ethz.ch%2Fmailman%2Flistinfo%2Fbioc-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. 

	[[alternative HTML version deleted]]