[
https://jira.codehaus.org/browse/SUREFIRE-909?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=308893#comment-308893
]
Kristian Rosenvold commented on SUREFIRE-909:
---------------------------------------------
It has become somewhat of a surefire tradition to break this logic every time
it is touched. Hopefully this last refactoring simplified it enough to make
sure it does not break again.
Fixed in 8dbde6de81cddd7335a5768dc22d9c414db6ef86, this time with a Unit test.
> Wrong elapsed time calculation
> -------------------------------
>
> Key: SUREFIRE-909
> URL: https://jira.codehaus.org/browse/SUREFIRE-909
> Project: Maven Surefire
> Issue Type: Bug
> Components: Junit 4.x support
> Affects Versions: 2.12.3
> Environment: linux, likely others
> Reporter: nkeywal
> Fix For: 2.13
>
>
> It's a regression in 2.12.3 vs. the previous versions.
> See "Time elapsed: 251992 sec"
> 2.12.3
> Running my.Test
> Tests run: 1, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 252.358 sec
> <<< FAILURE!
> test(my.Test) Time elapsed: 251992 sec <<< FAILURE!
> java.lang.AssertionError: expected array was null
> 2.10 or 2.11 or 2.12.1 or 2.12.2
> Tests run: 1, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 252.444 sec
> <<< FAILURE!
> test(my.Test) Time elapsed: 252.194 sec <<< FAILURE!
> java.lang.AssertionError: expected array was null
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
