On Thu, Sep 18, 2014 at 01:44:55PM -0500, Segher Boessenkool wrote:
> I am testing a patch that is just
>
>
> diff --git a/contrib/dg-extract-results.py b/contrib/dg-extract-results.py
> index cccbfd3..3781423 100644
> --- a/contrib/dg-extract-results.py
> +++ b/contrib/dg-extract-results.py
> @@ -117,7 +117,7 @@ class Prog:
> self.tool_re = re.compile (r'^\t\t=== (.*) tests ===$')
> self.result_re = re.compile (r'^(PASS|XPASS|FAIL|XFAIL|UNRESOLVED'
> r'|WARNING|ERROR|UNSUPPORTED|UNTESTED'
> - r'|KFAIL):\s*(\S+)')
> + r'|KFAIL):\s*(.+)')
> self.completed_re = re.compile (r'.* completed at (.*)')
> # Pieces of text to write at the head of the output.
> # start_line is a pair in which the first element is a datetime
Tested that with four runs on powerpc64-linux, four configs each time;
test-summary
shows the same in all cases. Many lines have moved compared to without
the patch, but that cannot be helped. Okay for mainline?
2014-09-19 Segher Boessenkool <seg...@kernel.crashing.org>
contrib/
* dg-extract-results.py (Prog.result_re): Include options in test name.
> Relatedly, is it just me or are most lines of the test summaries (the "#"
> lines after "===") missing since the parallelisation patches?
This is still open.
I also did some timings for make -j60 -k check, same -m64,-m32,-m32/-mpowerpc64,
-m64/-mlra configs. A run takes 65m, is effectively 42x parallel, and has 15%
system time.
Segher
