builds have stopped building with windows 8 slaves

[Mike Caspar]

(I changed the IP addresses to not leak out IP addresses)

When windows 8 test machines are launched, I get this message from Blue Ocean.....

019-10-26T18:27:16.629Z] Unpacking https://repo.maven.apache.org/maven2/org/apache/maven/apache-maven/3.5.4/apache-maven-3.5.4-bin.zip to C:\Jenkins\tools\hudson.tasks.Maven_MavenInstallation\mvn on win2012-db2580

Remote call on JNLP4-connect connection from xx.yy.zz.aa/bb.cc.dd.zz:49187 failed

In console, I see this message.... (only a partial paste)...  

Nothing had changed except for an attempt to change url to new location for wiki changeover (also does not build when reverted).

Not sure if I should report this in infra or as a problem in workflow? Perhaps someone who knows can forward this along?

If you are interested an can help, check the latest builds for ironmq-notifier

Thanks

java.lang.OutOfMemoryError: Java heap space

11:27:19  Also:   org.jenkinsci.plugins.workflow.steps.FlowInterruptedException

11:27:19  at org.jenkinsci.plugins.workflow.cps.CpsBodyExecution.cancel(CpsBodyExecution.java:253)

11:27:19  at org.jenkinsci.plugins.workflow.steps.BodyExecution.cancel(BodyExecution.java:76)

11:27:19  at org.jenkinsci.plugins.workflow.cps.steps.ParallelStepExecution.stop(ParallelStepExecution.java:67)

11:27:19  at org.jenkinsci.plugins.workflow.cps.steps.ParallelStep$ResultHandler$Callback.checkAllDone(ParallelStep.java:147)

11:27:19  at org.jenkinsci.plugins.workflow.cps.steps.ParallelStep$ResultHandler$Callback.onFailure(ParallelStep.java:134)

11:27:19  at org.jenkinsci.plugins.workflow.cps.CpsBodyExecution$FailureAdapter.receive(CpsBodyExecution.java:361)

11:27:19  at com.cloudbees.groovy.cps.impl.ThrowBlock$1.receive(ThrowBlock.java:68)

11:27:19  at com.cloudbees.groovy.cps.impl.ConstantBlock.eval(ConstantBlock.java:21)

11:27:19  at com.cloudbees.groovy.cps.Next.step(Next.java:83)

11:27:19  at com.cloudbees.groovy.cps.Continuable$1.call(Continuable.java:174)

11:27:19  at com.cloudbees.groovy.cps.Continuable$1.call(Continuable.java:163)

11:27:19  at org.codehaus.groovy.runtime.GroovyCategorySupport$ThreadCategoryInfo.use(GroovyCategorySupport.java:129)

11:27:19  at org.codehaus.groovy.runtime.GroovyCategorySupport.use(GroovyCategorySupport.java:268)

11:27:19  at com.cloudbees.groovy.cps.Continuable.run0(Continuable.java:163)

11:27:19  at org.jenkinsci.plugins.workflow.cps.SandboxContinuable.access$001(SandboxContinuable.java:18)

11:27:19  at org.jenkinsci.plugins.workflow.cps.SandboxContinuable.run0(SandboxContinuable.java:51)

11:27:19  at org.jenkinsci.plugins.workflow.cps.CpsThread.runNextChunk(CpsThread.java:186)

11:27:19  at org.jenkinsci.plugins.workflow.cps.CpsThreadGroup.run(CpsThreadGroup.java:370)

11:27:19  at org.jenkinsci.plugins.workflow.cps.CpsThreadGroup.access$200(CpsThreadGroup.java:93)

11:27:19  at org.jenkinsci.plugins.workflow.cps.CpsThreadGroup$2.call(CpsThreadGroup.java:282)

11:27:19  at org.jenkinsci.plugins.workflow.cps.CpsThreadGroup$2.call(CpsThreadGroup.java:270)

11:27:19  at org.jenkinsci.plugins.workflow.cps.CpsVmExecutorService$2.call(CpsVmExecutorService.java:66)

11:27:19  at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)

11:27:19  at hudson.remoting.SingleLaneExecutorService$1.run(SingleLaneExecutorService.java:131)

11:27:19  at jenkins.util.ContextResettingExecutorService$1.run(ContextResettingExecutorService.java:28)

11:27:19  at jenkins.security.ImpersonatingExecutorService$1.run(Impersona

[Tim Jacomb]

Isn’t this the same as the previous email in this group about constant ci.jenkins.io failures?

--
You received this message because you are subscribed to the Google Groups "Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-de...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/f945662b-e451-4b4a-b45c-00fc6c87ca77%40googlegroups.com.

[Gavin]

There's some ongoing issues with ci.jenkins. I've seen a bunch of back and forth about it on IRC.

I think we have to wait it out or commit without it 

Gavin

[Mike Caspar]

Just saw the other thread as well.

Will stay out of conversation and try again tomorrow.

I suspect someone is already dealing with it.

Thanks.

Mike