CI problem

[Michael Nazzareno Trimarchi]

Hi all

I'm getting some problem on verification build
16:39:14 Cannot contact jnlp-maven-17-wxw3t:
hudson.remoting.ChannelClosedException: Channel
"hudson.remoting.Channel@583d05db:JNLP4-connect connection from
ec2-3-18-53-88.us-east-2.compute.amazonaws.com/3.18.53.88:38039":
Remote call on JNLP4-connect connection from
ec2-3-18-53-88.us-east-2.compute.amazonaws.com/3.18.53.88:38039
failed. The channel is closing down or has closed down

Are people aware of this?

Michael


--
Michael Nazzareno Trimarchi
Co-Founder & Chief Executive Officer
M. +39 347 913 2170
mic...@amarulasolutions.com
__________________________________

Amarula Solutions BV
Joop Geesinkweg 125, 1114 AB, Amsterdam, NL
T. +31 (0)85 111 9172
in...@amarulasolutions.com
www.amarulasolutions.com

[Mark Waite]

On Monday, February 19, 2024 at 8:42:37 AM UTC-7 Michael wrote:

Hi all

I'm getting some problem on verification build
16:39:14 Cannot contact jnlp-maven-17-wxw3t:
hudson.remoting.ChannelClosedException: Channel
"hudson.remoting.Channel@583d05db:JNLP4-connect connection from
ec2-3-18-53-88.us-east-2.compute.amazonaws.com/3.18.53.88:38039":

We use spot instances for many of our builds with automatic retry if a spot instance is reclaimed by the cloud provider.  That can result in agent failures, though they should retry automatically.

One the GitHub checks page, you should see a "Re-run" action that will allow you to start a ci.jenkins.io job again.