-
Notifications
You must be signed in to change notification settings - Fork 30.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
The duration_ms is now broken on Jenkins #9784
Comments
raised an issue here: https://issues.jenkins-ci.org/browse/JENKINS-40033 |
My idea of the way forward here is replacing the tap plugin with |
Whats left to do is more testing plus making sure all workers have pip/tap2junit installed. At least AIX and debian7 hosts still lacks it. I have a fix for the later in my build branch. |
@gibfahn is this still an issue? |
@evanlucas yes it's still an issue, the duration reporting in Jenkins is still wrong. |
I don't get the problem with the time presented in the upper right. In the screenshot in this issue, 5min 18sec is surely the right duration for all the tests to run, not something 1000 times smaller or larger. What am I overlooking? |
That's the time it took the job to run, Jenkins has no problem with that as it's a Jenkins native measurement. The problem is the duration of each of the individual tests. They all show 0ms because their duration has been divided by 1000. The parsing of the |
As previously mentioned here, the Jenkins TAP plugin introduced a breaking change, so
duration_ms
really does now mean duration in milliseconds. However, the total time taken (top right in the screenshot) still assumesduration_ms
is in seconds (as it used to be, and astools/test.py
assumes it to be).There's been no response to @rvagg's comment on the Jenkins TAP plugin PR, but I assume that's because it's not actively developed.
I'd suggest that the way forward is to submit a PR to the TAP plugin adding duration, and then update our scripts to use that.
Related:
Jenkins plugin PR: jenkinsci/tap-plugin#6 (comment)
#7133 #7216 #7214
The text was updated successfully, but these errors were encountered: