Skip to content

[Bioc-devel] no build reports (nor builds) for Windows in BioC 3.4

7 messages · Ramon Diaz-Uriarte, Andrzej Oleś, Martin Morgan

#
Dear All,

During at least the last eight days I think there have been no new builds,
nor build reports, for BioC 3.4 (devel):

http://bioconductor.org/checkResults/devel/bioc-LATEST/

Is this on purpose?


Best,


R.
#
Hi Ramon,

why do you think there have been no build in the past week? The header on
the page you provided says:

*This page was generated on 2016-07-03 15:29:33 -0700 (Sun, 03 Jul 2016).*
svn.

Maybe some browser caching issue on your side?

Cheers,
Andrzej

On Mon, Jul 4, 2016 at 12:50 PM, Ramon Diaz-Uriarte <rdiaz02 at gmail.com>
wrote:

  
  
#
Hi Andrezj,

Sorry, the text of the message was not explicit (but the subject message
was): no builds for **Windows**.

So, yes, the page says "This page was generated on 2016-07-03 15:29:33
-0700 (Sun, 03 Jul 2016)."

but there are not reports for Windows, only for machines zin1 (Linux) and
Morelia (Mac). You can also see this if, from the page of any package in
devel, you click on the build status badge: you only get them from zin1 and
morelia, not for any windows machine.

And for at least some packages, the Windows version is lagging behind the
Linux and Macs versions (consistent with the idea of no builds for at least
a weak).



Best,



R.
On Mon, 04-07-2016, at 13:02, Andrzej Ole? <andrzej.oles at gmail.com> wrote:

  
    
#
I'm sorry, I didn't notice the Windows part in the message subject.

Indeed, the windows builder in devel seems to be offline. For example, the
the latest version of BiocStyle available from the website is 2.1.4, while
the subsequent version 2.1.5 was committed almost a month ago on Jun 9.

I'm not sure what happened to the windows machine, maybe someone from the
core team has more insight into this.

Cheers,
Andrzej

On Mon, Jul 4, 2016 at 2:10 PM, Ramon Diaz-Uriarte <rdiaz02 at gmail.com>
wrote:

  
  
#
On 07/04/2016 09:13 AM, Andrzej Ole? wrote:
There is a problem where one or more packages spawn processes that are 
not killed by the build system code. These then break subsequent steps. 
This has proved difficult to trouble-shoot, but is being worked on.

Sorry for the problems.

Martin
This email message may contain legally privileged and/or...{{dropped:2}}
#
Dear Andrzej,
On Mon, 04-07-2016, at 15:13, Andrzej Ole? <andrzej.oles at gmail.com> wrote:
I should have been explicit in the message body. My fault.
Thanks for confirming. And thanks for that example (the ones I checked were
only a week to 10 days old).
Best,

R.

P.S. Sorry for misspelling your name in the previous email  :-)

  
    
#
Thanks for looking into this Martin.

Best,

R.
On Mon, 04-07-2016, at 15:20, Martin Morgan <martin.morgan at roswellpark.org> wrote: