blob: ca107bc29b9f33d1062a54d98b296de640729fe7 [file] [log] [blame]
Daniel Dunbar40b65002016-09-26 23:38:23 +00001# Check the behavior of --max-failures option.
2#
Reid Klecknerc9e70002017-07-26 22:57:32 +00003# RUN: not %{lit} -j 1 -v %{inputs}/max-failures > %t.out
4# RUN: not %{lit} --max-failures=1 -j 1 -v %{inputs}/max-failures >> %t.out
5# RUN: not %{lit} --max-failures=2 -j 1 -v %{inputs}/max-failures >> %t.out
6# RUN: not %{lit} --max-failures=0 -j 1 -v %{inputs}/max-failures 2>> %t.out
Daniel Dunbar40b65002016-09-26 23:38:23 +00007# RUN: FileCheck < %t.out %s
8#
9# END.
10
Joel E. Denny31b37392018-05-31 00:55:32 +000011# CHECK: Failing Tests (27)
Daniel Dunbar40b65002016-09-26 23:38:23 +000012# CHECK: Failing Tests (1)
13# CHECK: Failing Tests (2)
14# CHECK: error: Setting --max-failures to 0 does not have any effect.