The last duration value displayed in the All view (and possibly other views) only shows the last successful build's duration. I guess I would have expected the duration of the last build, regardless of status.

Prereqs: You will need python, the py.test addon (easy_install pytest), and the file system SCM plugin for jenkins.

To duplicate, create a free-form job. Copy the attached sample python unit test file to an area such as ~/tmp. Using the file system SCM plugin, point it at ~/scm. For the build step, choose 'shell' and use 'py.test --junitxml=results.xml' Now kick off the build. The test will pass, and the Last Duration on the main page will probably show something like 1.0 - 1.5s.

Now, edit the provided sample unit test file. Change the sleep value to something longer (60) and make the assertion fail (1,1 --> 1,2). Kick off the build again. Now the build will fail. On the main page, the Last Duration still shows 1.0 - 1.5s. However, if you go to the lastBuild for the job, the duration in the upper right is correct and says something like "Took 1 min 0 sec", providing a link to the Build Time Trend.

If this is the default behavior for Last Duration, I understand. But is it possible that it can be made configurable so that I can still see how long my failing unit tests are taking?