-
Bug
-
Resolution: Fixed
-
Major
-
None
-
1.480.3 (reported), 1.515-SNAPSHOT on Linux (reproduced)
Created a test job
<?xml version='1.0' encoding='UTF-8'?> <project> <actions/> <description></description> <keepDependencies>false</keepDependencies> <properties/> <scm class="hudson.scm.NullSCM"/> <canRoam>true</canRoam> <disabled>false</disabled> <blockBuildWhenDownstreamBuilding>false</blockBuildWhenDownstreamBuilding> <blockBuildWhenUpstreamBuilding>false</blockBuildWhenUpstreamBuilding> <triggers class="vector"/> <concurrentBuild>false</concurrentBuild> <builders> <hudson.tasks.Shell> <command>for x in 0 1 2 3 4; do for y in 0 1 2 3 4; do for z in 0 1 2 3 4; do echo $x$y$z; cat /etc/pnm2ppa.conf; sleep 1; done; done; done</command> </hudson.tasks.Shell> </builders> <publishers/> <buildWrappers> <hudson.plugins.timestamper.TimestamperBuildWrapper plugin="timestamper@1.5.3"/> </buildWrappers> </project>
and ran it for a while, until there was enough output to truncate, then stopped it and compared .../console with .../consoleFull. The timestamps between the two are off by 1-2 seconds. For example, in console I see
14:51:31 + echo 021 14:51:31 021
whereas in consoleFull I see
14:51:33 + echo 021 14:51:33 021
and so on until the end of the file.
TimestampAnnotatorFactory.getOffset looked suspicious, though its default of 150Kb does still match the current value in Run/console.jelly.
- is duplicated by
-
JENKINS-18795 Timestamper sometimes does not update its timestamps
- Closed
-
JENKINS-17697 Different timestamp between short and full console log on timeout
- Closed