[JIRA] (JENKINS-55215) Log from cmake/ctest steps isn't fully captured on OsX
Title: Message Title Marian Klymov commented on JENKINS-55215 Re: Log from cmake/ctest steps isn't fully captured on OsX I've tried on another project - sleep hasn't helped there 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-55215) Log from cmake/ctest steps isn't fully captured on OsX
Title: Message Title Marian Klymov commented on JENKINS-55215 Re: Log from cmake/ctest steps isn't fully captured on OsX 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. 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-55215) Log from cmake/ctest steps isn't fully captured on OsX
Title: Message Title Marian Klymov commented on JENKINS-55215 Re: Log from cmake/ctest steps isn't fully captured on OsX Output isn't fully showing even STDOUT. Maybe it has something to do with https://issues.jenkins-ci.org/browse/JENKINS-32191 ? 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-55215) Log from cmake/ctest steps isn't fully captured on OsX
Title: Message Title
Marian Klymov created an issue
Jenkins / JENKINS-55215
Log from cmake/ctest steps isn't fully captured on OsX
Issue Type:
Bug
Assignee:
Martin Weber
Attachments:
log_race.png, log_race2.png, log_race3.png
Components:
cmakebuilder-plugin
Created:
2018-12-16 12:27
Environment:
Jenkins 2.150.1 CMake plugin 2.6.0 Pipeline 2.6 macOS 10.13.6 Remoting version: 3.27
Labels:
log cmake
Priority:
Minor
Reporter:
Marian Klymov
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.
[JIRA] (JENKINS-50350) JEP-200: ConversionException: Refusing to unmarshal logPrefixCache
Title: Message Title Marian Klymov commented on JENKINS-50350 Re: JEP-200: ConversionException: Refusing to unmarshal logPrefixCache I've checked some of them. Indeed, they were using version before fix: workflow-job@1.13 Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-50350) JEP-200: ConversionException: Refusing to unmarshal logPrefixCache
Title: Message Title Marian Klymov created an issue Jenkins / JENKINS-50350 JEP-200: ConversionException: Refusing to unmarshal logPrefixCache Issue Type: Bug Assignee: Unassigned Components: workflow-job-plugin Created: 2018-03-22 20:26 Environment: Jenkins 2.107.1 Pipeline: Job 2.17 Labels: JEP-200 log pipeline Priority: Minor Reporter: Marian Klymov I'm getting lots of "Unreadable data" from different pipelines after upgrade to 2.107.1. ConversionException: Refusing to unmarshal logPrefixCache for security reasons; see https://jenkins.io/redirect/class-filter/ Debugging information class : com.google.common.cache.LocalCache$LocalLoadingCache required-type : com.google.common.cache.LocalCache$LocalLoadingCache converter-type : hudson.util.XStream2$BlacklistedTypesConverter path : /flow-build/logPrefixCache line number : 214 --- line numbers: 134, 214, 222, 238, 313, 391 etc. On first look log seems to be normal for mentioned build numbers. Is this something that I need to be worried about?
