[JIRA] (JENKINS-59907) sh steps stuck indefinitely on uncommon architectures (e.g. s390x)

2019-10-31 Thread jakub.lou...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jakub L commented on  JENKINS-59907  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: sh steps stuck indefinitely on uncommon architectures (e.g. s390x)   
 

  
 
 
 
 

 
 I can confirm that v1.33 works fine on s390x. Thanks for the fix!  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)  
 
 

 
   
 

  
 

  
 

   





-- 
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.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202658.1571858325000.6282.1572545880500%40Atlassian.JIRA.


[JIRA] (JENKINS-59907) sh steps stuck indefinitely on uncommon architectures (e.g. s390x)

2019-10-24 Thread jakub.lou...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jakub L updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-59907  
 
 
  sh steps stuck indefinitely on uncommon architectures (e.g. s390x)   
 

  
 
 
 
 

 
Change By: 
 Jakub L  
 
 
Summary: 
 sh steps stuck indefinitely  after upgrading durable-task to v1  on uncommon architectures (e . 31 g. s390x)  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)  
 
 

 
   
 

  
 

  
 

   





-- 
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.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202658.1571858325000.177.1571907780515%40Atlassian.JIRA.


[JIRA] (JENKINS-59907) sh steps stuck indefinitely after upgrading durable-task to v1.31

2019-10-24 Thread jakub.lou...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jakub L commented on  JENKINS-59907  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: sh steps stuck indefinitely after upgrading durable-task to v1.31   
 

  
 
 
 
 

 
 This is NOT related to the other two opened issues with v1.31. Those two are likely caused by the new binary durable_task_monitor not being available from within Docker containers. But this issue is caused by the binary not being executable on my HW architecture. I'll clarify the title.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)  
 
 

 
   
 

  
 

  
 

   





-- 
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.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202658.1571858325000.174.1571907660256%40Atlassian.JIRA.


[JIRA] (JENKINS-59906) durable-task plugin v1.31 fails to execute shell commands on swarm client

2019-10-23 Thread jakub.lou...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jakub L commented on  JENKINS-59906  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: durable-task plugin v1.31 fails to execute shell commands on swarm client   
 

  
 
 
 
 

 
 What architecture is your client running on? If it's not Linux or MacOS running on amd64 or i386, then the problem lies in the newly added golang binary durable_task_monitor. If that's the case, this issue is related to JENKINS-59907.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)  
 
 

 
   
 

  
 

  
 

   





-- 
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.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202656.1571852611000.18541.1571858940148%40Atlassian.JIRA.


[JIRA] (JENKINS-59907) sh steps stuck indefinitely after upgrading durable-task to v1.31

2019-10-23 Thread jakub.lou...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jakub L created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-59907  
 
 
  sh steps stuck indefinitely after upgrading durable-task to v1.31   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Unassigned  
 
 
Components: 
 durable-task-plugin  
 
 
Created: 
 2019-10-23 19:18  
 
 
Environment: 
 Jenkins ver. 2.201 (yum installed, master node only)  durable-task plugin v1.31   os.arch: s390x  os.name: Linux (RedHat)  os.version: 3.10.0-327.el7.s390x  
 
 
Priority: 
  Major  
 
 
Reporter: 
 Jakub L  
 

  
 
 
 
 

 
 After upgrading to v1.31, the first sh step in a pipeline gets stuck. After few minutes Console Output shows: 

[Pipeline] sh (Get email of the author of last commit) process apparently never started in /data/jenkins/workspace/TG2_PTG2_-_pipeline_build_master@tmp/durable-be2cf2a6 (running Jenkins temporarily with -Dorg.jenkinsci.plugins.durabletask.BourneShellScript.LAUNCH_DIAGNOSTICS=true might make the problem clearer) Cannot contact : java.io.FileNotFoundException: File '/data/jenkins/workspace/TG2_PTG2_-_pipeline_build_master@tmp/durable-be2cf2a6/output.txt' does not exist
   Eventually, I discovered that a new binary was added in the latest version of this plugin. The script compile-binaries.sh in GitHub suggests that the binary is only built for Linux and MacOS.   Sure enough, when I try to execute the binary myself on an architecture other than amd64, I get: 

-bash: /data/jenkins/caches/durable-task/durable_task_monitor_1.31_unix_64: cannot execute binary file
   Are other architectures or operat