-
Bug
-
Resolution: Unresolved
-
Minor
-
None
-
Jenkins 2.303.1
Timestamper 1.13 (recent)
RH7, no container
I see timestamps, which don't look reasonable in console log.
I'm using bash with '-x' to get a trace of my shell script in console log. The examples are showing "elapsed time"
E.g.:
00:12:19.672 ++ python3 cov-reports.py ...00:12:19.672 ++ ret=0*00:12:24.416* ++ ccp /var/fpwo
The first python command needs ~ 5 seconds (cross checked with "time" on command line)
This "ret=0" is a "ret=$?" in the following line, to catch and save the command exit value. Here I would expect the accumulated time of the command. But the timestamp stays unchanged.
Only the next line shows the accumulated time. I would have expected this timestamp on the previous line.
Confusing but good example:
00:12:15.608 +++ cov-manage-im -...00:12:15.609 +++ wc -l*00:12:15.609* ++ defectCount=0*00:12:19.659* ++ [[ 0 -ne 0 ]]
The first three lines are a pipeline, so I see only in the last line, the accumulated time of the pipeline. So this is confusing at first sight, but correct.