When the previous build had test failures and the current build did not
produce any test results, Vulcan carries over the previous failures to keep
track of when the tests were first broken. This behavior can be confusing.
A message should be shown to the user indicating more clearly why the test
failures are being carried over.
Original issue reported on code.google.com by chris.eldredge@gmail.com on 11 Dec 2009 at 2:52
Original issue reported on code.google.com by
chris.eldredge@gmail.com
on 11 Dec 2009 at 2:52