Commit 175d49e6 authored by Ben Gamari's avatar Ben Gamari 🐢
Browse files

testsuite: Introduce fragile modifier

Now since we have been a bit more stringent in testsuite cleanliness we
have been marking a lot of tests as fragile using the `skip` modifier.
However, this unfortunately means that we lose the association with the
ticket number documenting the fragility.

Here we introduce `fragile` and `fragile_for` to retain this
information.

(cherry picked from commit 4ca271d1)
parent 983ada70
......@@ -225,6 +225,30 @@ def _expect_pass(way):
# -----
def fragile( bug ):
"""
Indicates that the test should be skipped due to fragility documented in
the given ticket.
"""
def helper( name, opts, bug=bug ):
record_broken(name, opts, bug)
opts.skip = True
return helper
def fragile_for( name, opts, bug, ways ):
"""
Indicates that the test should be skipped due to fragility in the given
test ways as documented in the given ticket.
"""
def helper( name, opts, bug=bug, ways=ways ):
record_broken(name, opts, bug)
opts.omit_ways = ways
return helper
# -----
def omit_ways( ways ):
return lambda name, opts, w=ways: _omit_ways( name, opts, w )
......
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment