I wrote a small tool to generate html tables from the testsuite logs, an example is here: http://dl.dropbox.com/u/24218791/gdc-testsuite/testsuite.html

I'll publish the tool/sources soon.

Current features:
 * Summary of the test results (overall, compilable, runnable,
   fail_compilation)
 * Detailed test results
 * Test names are linked to test case files on github
 * architecture names can be linked to custom locations
 * CSS tooltips display extended information about the test
   architecture & test results
 * the detailed tests link to the correct line in the output log.
   This seems to work fine afaics, although it's a stress test for
   webbrowsers as the log files are quite big

On 23-08-2012 19:13, Johannes Pfau wrote:
> I wrote a small tool to generate html tables from the testsuite logs,
> an example is here:
> http://dl.dropbox.com/u/24218791/gdc-testsuite/testsuite.html
>
> I'll publish the tool/sources soon.
>
> Current features:
>   * Summary of the test results (overall, compilable, runnable,
>     fail_compilation)
>   * Detailed test results
>   * Test names are linked to test case files on github
>   * architecture names can be linked to custom locations
>   * CSS tooltips display extended information about the test
>     architecture & test results
>   * the detailed tests link to the correct line in the output log.
>     This seems to work fine afaics, although it's a stress test for
>     webbrowsers as the log files are quite big
>

Very nice! This gives a great overview.

-- 
Alex Rønne Petersen
alex@lycus.org
http://lycus.org

On 23 August 2012 18:53, Alex Rønne Petersen <alex@lycus.org> wrote:
> On 23-08-2012 19:13, Johannes Pfau wrote:
>>
>> I wrote a small tool to generate html tables from the testsuite logs, an example is here: http://dl.dropbox.com/u/24218791/gdc-testsuite/testsuite.html
>>
>> I'll publish the tool/sources soon.
>>
>> Current features:
>>   * Summary of the test results (overall, compilable, runnable,
>>     fail_compilation)
>>   * Detailed test results
>>   * Test names are linked to test case files on github
>>   * architecture names can be linked to custom locations
>>   * CSS tooltips display extended information about the test
>>     architecture & test results
>>   * the detailed tests link to the correct line in the output log.
>>     This seems to work fine afaics, although it's a stress test for
>>     webbrowsers as the log files are quite big
>>
>
> Very nice! This gives a great overview.
>
> --
> Alex Rønne Petersen
> alex@lycus.org
> http://lycus.org

Wicked.

Bare in mind that the testsuite doesn't test a great range of switches at the moment.  I do plan to have the default set options to: '-g -O3 -funittest -frelease -finline-functions' - however this will take a rather longer time to run and produce a bigger log file. ;-)


Regards
-- 
Iain Buclaw

*(p < e ? p++ : p) = (c & 0x0f) + '0';

Am Thu, 23 Aug 2012 19:21:31 +0100
schrieb Iain Buclaw <ibuclaw@ubuntu.com>:
> 
> Wicked.
> 
> Bare in mind that the testsuite doesn't test a great range of switches at the moment.  I do plan to have the default set options to: '-g -O3 -funittest -frelease -finline-functions' - however this will take a rather longer time to run and produce a bigger log file. ;-)

I should update the tool to handle logs with multiple switches anyway. I guess I'll just split the logs so they don't get too big.

BTW: If you installed http://moinmo.in/MacroMarket/IncludeExternalFile we could embed the testsuite results into the wiki. As long as we don't use javascript in the html files and keep the html files in a secure location, there should be no security risk, afaics.

(I tried targetting wiki syntax, but that doesn't work well. Even colors won't work without extensions, tool tips probably not at all)

Am Thu, 23 Aug 2012 19:13:42 +0200
schrieb Johannes Pfau <nospam@example.com>:

> I wrote a small tool to generate html tables from the testsuite logs, an example is here: http://dl.dropbox.com/u/24218791/gdc-testsuite/testsuite.html
> 
> I'll publish the tool/sources soon.
> 

I uploaded the tool to github:
https://github.com/jpf91/test2html
The code is quite ugly though and I'll have to rewrite some parts of
it, but it's working.

The input log files are also available: https://github.com/jpf91/gdc-test-results