[Piglit] [PATCH] tests/igt.py: mark segfaulted IGT process as 'crash'

Martin Peres martin.peres at linux.intel.com
Wed Jun 14 10:24:15 UTC 2017


Reviewed-by: Martin Peres <martin.peres at linux.intel.com>

I will push the patch now. It has waited on the list long-enough!

Thanks,
Martin

On 16/05/17 18:08, Tomi Sarvela wrote:
> On IGT testing segfaulted processes are lumped together with failed
> tests in results. This patch separates the two for correctness: test
> doesn't have opportunity to fail if it wasn't even run.
> 
> On our testing environment segfaulted IGT tests point to problem on
> builder or testhost side, not to the testcase itself.
> 
> Signed-off-by: Tomi Sarvela <tomi.p.sarvela at intel.com>
> ---
>   tests/igt.py | 2 ++
>   1 file changed, 2 insertions(+)
> 
> diff --git a/tests/igt.py b/tests/igt.py
> index 87b61dc..e6d3963 100644
> --- a/tests/igt.py
> +++ b/tests/igt.py
> @@ -122,6 +122,8 @@ class IGTTest(Test):
>               self.result.result = 'skip'
>           elif self.result.returncode == 78:
>               self.result.result = 'timeout'
> +        elif self.result.returncode == 139:
> +            self.result.result = 'crash'
>           else:
>               self.result.result = 'fail'
>   
> 


More information about the Piglit mailing list