[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: [PATCH] Junit report for Subversion tests

From: Gavin Baumanis <gavinb_at_thespidernet.com>
Date: Tue, 3 Nov 2009 10:18:27 +1100

Hi All,

Although there is a patch submission - there was a quite a bit of
discussion too.
Though there doesn't seem to have been an agreement or a subsequent
patch submission (if at all needed).
But since it has been a week now without activity I thought I would
bring it back up the list - in case it had fallen off people's radar.

Gavin.

On 27/10/2009, at 14:55 , Branko Cibej wrote:

> Hyrum K. Wright wrote:
>> On Oct 22, 2009, at 1:17 PM, Bhuvaneswaran A wrote:
>>
>>
>>> The sum of all >1 seconds test cases sum up to 12.6 minutes.
>>>
>>
>> That does seem rather quick. I just ran 'make check' on a separate
>> working copy on the same machine, and got something different:
>> real 32m51.756s
>> user 6m40.321s
>> sys 6m27.504s
>>
>> I don't know that this is a problem with the junit converter script,
>> or perhaps the test running reporting bogus ELAPSED times.
>>
>
> Apparently it's quite reasonable. As I posted elsewhere, I got a
> similar
> "real" time on my laptop (with tmpfs and cleanups and parallel test
> executions), but my user time was almost 22 minutes. And I have an
> elapsed time for commit-tests.py under one minute. While it's easy to
> imagine this being twice as fast on a real machine with something more
> than this trundle for a CPU, I can hardly imagine how that would be
> truncated to 0 seconds.
>
> -- Brane
>
> ------------------------------------------------------
> http://subversion.tigris.org/ds/viewMessage.do?dsForumId=462&dsMessageId=2411585

------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=462&dsMessageId=2413974
Received on 2009-11-03 00:18:47 CET

This is an archived mail posted to the Subversion Dev mailing list.