[JIRA] (JENKINS-57229) Slave exception while serializing back to master

2019-04-29 Thread jgl...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jesse Glick started work on  JENKINS-57229  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
Change By: 
 Jesse Glick  
 
 
Status: 
 Open In Progress  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-57229) Slave exception while serializing back to master

2019-04-29 Thread jgl...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jesse Glick assigned an issue to Jesse Glick  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-57229  
 
 
  Slave exception while serializing back to master   
 

  
 
 
 
 

 
Change By: 
 Jesse Glick  
 
 
Assignee: 
 Jesse Glick  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-57229) Slave exception while serializing back to master

2019-04-29 Thread jgl...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jesse Glick updated  JENKINS-57229  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-57229  
 
 
  Slave exception while serializing back to master   
 

  
 
 
 
 

 
Change By: 
 Jesse Glick  
 
 
Status: 
 In  Progress  Review  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-57229) Slave exception while serializing back to master

2019-04-29 Thread jgl...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jesse Glick updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-57229  
 
 
  Slave exception while serializing back to master   
 

  
 
 
 
 

 
 

 

Failed to serialize hudson.plugins.clover.CloverHtmlBuildAction#buildReportPath for class hudson.plugins.clover.CloverHtmlBuildAction
 

 indicates a bug in the Clover plugin.  
 

  
 
 
 
 

 
Change By: 
 Jesse Glick  
 
 
Component/s: 
 clover-plugin  
 
 
Component/s: 
 core  
 
 
Component/s: 
 junit-plugin  
 
 
Labels: 
 junit-plugin  regression  
 

  
 
 
 
 

 
  This exception happens in a jenkins pipeline. I successfully eliminated it by removing all junit 'build/xx' calls from the pipeline. According tu Jenkins we are running the Junit plugin version 1.27. Jenkins is version 2.175. We are running slave nodes using ssh. JVM is  openjdk-8-jre:amd64 8u191-b12-2ubuntu0.18.04.1 on both instandes.The stacktrace  we get is:{noformat}hudson.remoting.ProxyException: java.io.NotSerializableException: The calling thread Thread[org.jenkinsci.plugins.workflow.steps.SynchronousNonBlockingStepExecution [#6],5,main] has no associated channel. The current object /var/lib/jenkins/jobs/elev/builds/3250 is interface org.jenkinsci.remoting.SerializableOnlyOverRemoting, but it is likely being serialized/deserialized without the channel at org.jenkinsci.remoting.SerializableOnlyOverRemoting.getChannelForSerialization(SerializableOnlyOverRemoting.java:67) at hudson.FilePath.writeObject(FilePath.java:2989) at sun.reflect.GeneratedMethodAccessor87.invoke(Unknown Source) at 

[JIRA] (JENKINS-57229) Slave exception while serializing back to master

2019-04-29 Thread o.v.nenas...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Oleg Nenashev commented on  JENKINS-57229  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Slave exception while serializing back to master   
 

  
 
 
 
 

 
 Serializing FilePath to Pipeline context...   
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-57229) Slave exception while serializing back to master

2019-04-29 Thread o.v.nenas...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Oleg Nenashev commented on  JENKINS-57229  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Slave exception while serializing back to master   
 

  
 
 
 
 

 
 Jesse Glick this is a regression after  https://github.com/jenkinsci/jenkins/pull/3980 / JENKINS-47896 . Have not checked yet whether it is a valid one  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-57229) Slave exception while serializing back to master

2019-04-29 Thread o.v.nenas...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Oleg Nenashev updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-57229  
 
 
  Slave exception while serializing back to master   
 

  
 
 
 
 

 
Change By: 
 Oleg Nenashev  
 
 
Labels: 
 junit-plugin  regression  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-57229) Slave exception while serializing back to master

2019-04-29 Thread tarjei.h...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Tarjei Huse created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-57229  
 
 
  Slave exception while serializing back to master   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Unassigned  
 
 
Components: 
 core, junit-plugin  
 
 
Created: 
 2019-04-29 19:22  
 
 
Environment: 
 Ubuntu Linux 18.04 on both slave and master.  
 
 
Labels: 
 junit-plugin  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Tarjei Huse  
 

  
 
 
 
 

 
 This exception happens in a jenkins pipeline. I successfully eliminated it by removing all  junit 'build/xx'  calls from the pipeline.  According tu Jenkins we are running the Junit plugin version 1.27. Jenkins is version 2.175. We are running slave nodes using ssh.  JVM is openjdk-8-jre:amd64 8u191-b12-2ubuntu0.18.04.1 on both instandes. The stacktrace we get is: 

 

hudson.remoting.ProxyException: java.io.NotSerializableException: The calling thread Thread[org.jenkinsci.plugins.workflow.steps.SynchronousNonBlockingStepExecution [#6],5,main] has no associated channel. The current object /var/lib/jenkins/jobs/elev/builds/3250 is interface org.jenkinsci.remoting.SerializableOnlyOverRemoting, but it is likely being serialized/deserialized without the channel
 at org.jenkinsci.remoting.SerializableOnlyOverRemoting.getChannelForSerialization(SerializableOnlyOverRemoting.java:67)
 at hudson.FilePath.writeObject(FilePath.java:2989)
 at sun.reflect.GeneratedMethodAccessor87.invoke(Unknown Source)
 at