Closed
Bug 558384
Opened 14 years ago
Closed 14 years ago
testconfig include directive should take precedence over a skip directive
Categories
(Tamarin Graveyard :: Tools, defect)
Tamarin Graveyard
Tools
Tracking
(Not tracked)
VERIFIED
FIXED
Q3 11 - Serrano
People
(Reporter: cpeyer, Assigned: cpeyer)
Details
Attachments
(1 file)
1.24 KB,
patch
|
brbaker
:
review+
|
Details | Diff | Splinter Review |
If a test is 'skip'ed globally (.*) and then included for a specific configuration, the test is still skipped for the included config.
Assignee | ||
Comment 1•14 years ago
|
||
Make include override any skip command defined for the same configuration: even if a test is skipped and included for the exact same config string, include takes precedence - testconfig sample: misc/catchableTimeout, .*deep, skip, skip slow tests misc/catchableTimeout, .*deep, include, include slow tests in deep phase given the above, catchableTimeout will still run in deep configurations
Updated•14 years ago
|
Attachment #438137 -
Flags: review?(brbaker) → review+
Assignee | ||
Comment 2•14 years ago
|
||
Just to clarify - the typical setup for deep tests in testconfig would be: misc/catchableTimeout, .*, skip, skip slow tests misc/catchableTimeout, .*deep, include, include slow tests in deep phase The example in comment #1 was to demonstrate that include will override skip no matter what.
Assignee | ||
Comment 3•14 years ago
|
||
pushed to tr and argo: changeset 4374 657134ccf268
Status: ASSIGNED → RESOLVED
Closed: 14 years ago
Resolution: --- → FIXED
Assignee | ||
Updated•14 years ago
|
Status: RESOLVED → VERIFIED
You need to log in
before you can comment on or make changes to this bug.
Description
•