Blue Ocean test results show incorrect time

[Daniel Becroft]

Hi,

I have started to use the pipeline with NUnit, but the test result timing appear incorrectly. In Blue Ocean, the time elapsed is always < 1s, whereas the correct time displays in Classic Jenkins.

Should this be raised with the individual plugin maintainer (which project would that be?), or is it a general BO issue?

Cheers,

Daniel B.

[Steven Foster]

I just had this problem in the opposite direction, where Jenkins Classic seemed to report way too long durations for every test. It seems JUnit expects a duration in seconds, and I had been providing a duration in milliseconds. Blue ocean seemed to handle the milliseconds fine.

Now that I've changed to seconds, Jenkins Classic shows correct durations and blue ocean shows <1s as you describe.

[Daniel Becroft]

"Now that I've changed to seconds" - how do you mean? Do you mean your tests have elapsed to more than 1s in duration, or something else?

---
Daniel Becroft

On Mon, Jul 16, 2018 at 11:19 PM Steven Foster <steven...@gmail.com> wrote:

I just had this problem in the opposite direction, where Jenkins Classic seemed to report way too long durations for every test. It seems JUnit expects a duration in seconds, and I had been providing a duration in milliseconds. Blue ocean seemed to handle the milliseconds fine.

Now that I've changed to seconds, Jenkins Classic shows correct durations and blue ocean shows <1s as you describe.

--
You received this message because you are subscribed to the Google Groups "Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-use...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/09e664f0-8d77-4412-a92f-d0c903ccdff2%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Steven Foster]

Oh sorry, I should mention that I am generating the XML myself with my own tool so I have full control over the output. I was using milliseconds in the xml, but I switched it to seconds (with decimals). With existing tools this might not be possible.

[Sean Talts]

I'm also having this problem - I would be fine with Jenkins requiring either ms or s, but we use the performance test components which are in classic view and assuming times are in seconds, while blue ocean assumes times are in milliseconds. Seems like a bug to me.

[Craig Rodrigues]

I encountered the same problem and reported the issue here:

https://issues.jenkins-ci.org/browse/JENKINS-52944

--

Craig

--
You received this message because you are subscribed to the Google Groups "Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-use...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/0d9783e9-4c72-4cbf-8b54-9fe85984fa63%40googlegroups.com.