René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"The duration_ms is now broken on Jenkins","articleBody":"* **Subsystem**: test, jenkins\r\n\r\nAs previously mentioned [here](https://github.com/nodejs/node/pull/7216#issuecomment-224594136), 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 assumes `duration_ms` is in seconds (as it used to be, and as `tools/test.py` assumes it to be).\r\n\r\nThere's been no response to @rvagg's comment on [the Jenkins TAP plugin PR](https://github.com/jenkinsci/tap-plugin/pull/6#issuecomment-224763190), but I assume that's because it's not actively developed. \r\n\r\nI'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.\r\n\r\n![image](https://cloud.githubusercontent.com/assets/15943089/20597849/f38752a0-b23d-11e6-8694-044ccc0f6588.png)\r\n\r\nRelated:\r\nJenkins plugin PR: https://github.com/jenkinsci/tap-plugin/pull/6#issuecomment-224763190\r\nhttps://github.com/nodejs/node/pull/7133 https://github.com/nodejs/node/pull/7216 https://github.com/nodejs/node/pull/7214","author":{"url":"https://github.com/gibfahn","@type":"Person","name":"gibfahn"},"datePublished":"2016-11-24T12:22:35.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":8},"url":"https://github.com/9784/node/issues/9784"}