On Mon, Oct 26, 2009 at 10:02 AM, Bhuvaneswaran A <bhuvan_at_collab.net> wrote:
> On Mon, 2009-10-26 at 08:54 -0400, Mark Phippard wrote:
>> I do not understand how this accounts for such a big discrepancy in
>> the time reported? For example, as I pointed out, the entire
>> commit_tests.py reports as taking 0ms. How is including and not
>> rounding the milliseconds going to suddenly make that reports as the
>> several minutes that it in fact does take?
> I'll explain the issue using the commit_tests.py test suite.
> Originally, the commit_tests.py test suite has taken 39 seconds to
> complete. In total, there are 62 tests comprising this test suite. The
> time taken by each test is set as 0 seconds in the junit file instead of
> 0.62 seconds (39/62). Due to this fact, the Hudson set the total time
> taken for this test suite as 0 (0*62). It is irrespective of the fact
> that the actual time for this test suite is defined as 39 seconds in the
> junit file, globally.
>> As someone else speculated, is it possible that the test setup and
>> teardown is not being included in the times?
> The ELAPSED: line in tests.log prints the *exact* time taken to execute
> each test suite. If the setup/teardown part is not performed within
> START/END of test suite, then yes, it's not included.
> I'll look into this, once we are done with the known bug. Thanks!
OK, thanks. I thought those tests took a few minutes on my system,
but if they run that fast, then maybe that explains it?
Received on 2009-10-26 15:09:01 CET