[JENKINS-55215] Log from cmake/ctest steps isn't fully captured on OsX

[jenkins-infra-bot]

After some updates I've noticed that console isn't showing full log for cmake build and ctest run steps.

"try {
...
cmakeBuild buildDir: ..., cmakeArgs: cmake_params, generator: 'Xcode', installation: '(default)', sourceDir: source_dir, steps: [[args: '--config '+BuildConfiguration+' -- -j 4 -quiet', withCmake: true]]
if (RunTests.toBoolean())

{ ctest arguments: '-C '+BuildConfiguration+' --output-on-failure', installation: '(default)', workingDir: ... }

} finally {
sh 'umount ${WORKSPACE}/mnt/ThirdParties || true'
}"

I'm attaching examples. In one case there were failing unittests, but 'sh' step is shown in the middle of ctest log. In other cases with successful unittests log is missing last steps and some additional info from ctest.

---

Originally reported by nekto, imported from: Log from cmake/ctest steps isn't fully captured on OsX

• status: Open
• priority: Minor
• component(s): cmakebuilder-plugin
• label(s): cmake, log, pipeline
• resolution: Unresolved
• votes: 0
• watchers: 2
• imported: 20260124-160229

Raw content of original issue

After some updates I've noticed that console isn't showing full log for cmake build and ctest run steps.

"try {
 ...
 cmakeBuild buildDir: ..., cmakeArgs: cmake_params, generator: 'Xcode', installation: '(default)', sourceDir: source_dir, steps: [[args: '--config '+BuildConfiguration+' -- -j 4 -quiet', withCmake: true]]
 if (RunTests.toBoolean()) 
{
 ctest arguments: '-C '+BuildConfiguration+' --output-on-failure', installation: '(default)', workingDir: ...
 }
} finally {
 sh 'umount ${WORKSPACE}/mnt/ThirdParties || true'
}"

I'm attaching examples. In one case there were failing unittests, but 'sh' step is shown in the middle of ctest log. In other cases with successful unittests log is missing last steps and some additional info from ctest.

environment

Jenkins 2.150.1<br/>
CMake plugin 2.6.0<br/>
Pipeline 2.6<br/>
macOS 10.13.6<br/>
Remoting version: 3.27

3 attachments

• log_race.png

  

• log_race2.png

  

• log_race3.png

  

[jenkins-infra-bot]

15knots:

• Original comment link
• Raw content of original comment:

  Could it be that ANY output written to STDERR is missing in the logs?
  

Could it be that ANY output written to STDERR is missing in the logs?

[jenkins-infra-bot]

nekto:

• Original comment link
• Raw content of original comment:

  Output isn't fully showing even STDOUT. Maybe it has something to do with https://issues.jenkins-ci.org/browse/JENKINS-32191 ?
  
   
  

Output isn't fully showing even STDOUT. Maybe it has something to do with https://issues.jenkins-ci.org/browse/JENKINS-32191 ?

 

[jenkins-infra-bot]

15knots:

• Original comment link
• Raw content of original comment:

  Thanks for finding a related issue, I myself did not find one.
  
  The plugin does not do anything special to capture the build output. It just takes a TaskListener and a Launcher from the StepContext and passes the listener to the launcher. The listener is supposed to handle any build output.
  
  So I think this issue is related to JENKINS-32191, or at least to workflow plugin.
  
  Please note that JENKINS-32191 has been marked as resolved with <https://issues.jenkins-ci.org/browse/JENKINS-32191?focusedCommentId=350722&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-350722> but the reason to resolve it is just a guess. Have you tried with inserting a 'sleep 3' command into your script as a workaround?
  
   
  

Thanks for finding a related issue, I myself did not find one.

The plugin does not do anything special to capture the build output. It just takes a TaskListener and a Launcher from the StepContext and passes the listener to the launcher. The listener is supposed to handle any build output.

So I think this issue is related to JENKINS-32191">JENKINS-32191, or at least to workflow plugin.

Please note that JENKINS-32191">JENKINS-32191 has been marked as resolved with <https://issues.jenkins-ci.org/browse/JENKINS-32191?focusedCommentId=350722&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-350722> but the reason to resolve it is just a guess. Have you tried with inserting a 'sleep 3' command into your script as a workaround?

 

[jenkins-infra-bot]

nekto:

• Original comment link
• Raw content of original comment:

  I've added sleep for 5 seconds in the end after sh 'umount...'
  
  Now log for ctest step is fully shown.
  
  But still 'sh' step starts in the middle of ctest output.
  
   
  

I've added sleep for 5 seconds in the end after sh 'umount...'

Now log for ctest step is fully shown.

But still 'sh' step starts in the middle of ctest output.

 

[jenkins-infra-bot]

nekto:

• Original comment link
• Raw content of original comment:

  I've tried on another project - sleep hasn't helped there 
  
   
  

I've tried on another project - sleep hasn't helped there

 

[jenkins-infra-bot]

15knots:

• Original comment link
• Raw content of original comment:

  I tried to reproduce this on a remote Linux agent by generating lots of output.
  
  Pipeline script:
  
  node('linux') {
      timestamps {
          stage('all') {
     echo 'Hello World'
     sh label: 'ls', script: 'ls -lgGR /bin /lib /lib64 /opt /usr'
          }
      }
  }
  
  
  Unfortunately, I could not reproduce the issue.
  Could you try to runs the script on an OSX agent to verify whether it is related to cmakebuilder or to pipeline?
  

I tried to reproduce this on a remote Linux agent by generating lots of output.

Pipeline script:

node('linux') {
    timestamps {
stage('all') {
   echo 'Hello World'
   sh label: 'ls', script: 'ls -lgGR /bin /lib /lib64 /opt /usr'
}
    }
}

Unfortunately, I could not reproduce the issue.

Could you try to runs the script on an OSX agent to verify whether it is related to cmakebuilder or to pipeline?