Within a container, generated with kubernetes (using kubernetes-plugin), a simple process invocation will generate multiple time this log:

      ...
      Cannot contact kubernetes-c4df03a7122e48a5a094643522eca149-2f29e02b2bb2: java.io.IOException: corrupted content in /home/jenkins/workspace/POPOPOPO@tmp/durable-a2a574cd/pid: java.lang.NumberFormatException: For input string: ""
      ...
      

      Here is a simple pipeline to easily reproduce:

      podTemplate(label: 'mypod', containers: [])
      {
        stage("Test"){
            node("mypod"){
              container("jnlp"){
                sh '''
                echo "#!/bin/sh
      sleep 10" > popo.sh
                 chmod a+x popo.sh
                 ./popo.sh
                '''
              }
            }
        }
      }
      

      This seem to be happening with the last update of the durable-task-plugin.
      A rollback of the k8 plugin (to 0.10) didn't change anything.

      We don't know if it is a harmless log or is it a signal that something might go wrong.
      In both cases, the log is now less readable.

          [JENKINS-42316] Log report corrupted content in durable-*/pid

          Mike Splain added a comment -

          Yeah we're seeing this too, quite annoying.

          Mike Splain added a comment - Yeah we're seeing this too, quite annoying.

          Pavel Sadikov added a comment -

          Running into this as well, doesn't seem to cause any problems. Also hello Mike!

          Pavel Sadikov added a comment - Running into this as well, doesn't seem to cause any problems. Also hello Mike!

          Mike Splain added a comment -

          Oh hey sigmat, small world!

          Mike Splain added a comment - Oh hey sigmat , small world!

            csanchez Carlos Sanchez
            pascallap Pascal Laporte
            Votes:
            1 Vote for this issue
            Watchers:
            6 Start watching this issue

              Created:
              Updated:
              Resolved: