Details
-
Bug
-
Resolution: Won't Do
-
P3: Somewhat important
-
None
-
master
-
None
Description
Given example blacklist:
[qMessagePattern:backtrace] # QTBUG-63915 b2qt 64bit [qMessagePattern:backtrace depth,separator] # QTBUG-63915 b2qt 64bit
The blacklist tool will match qMessagePattern to the first item [qMessagePattern:backtrace]. Regardless of the action taken on the item, no option is provided to update other instances of qMessagePattern in the blacklist.
The tool should, at the outset, notify the user that there were multiple matches found, and request action on each.
Proposed flow:
- Multiple matches for ‘qMessagePattern’ found.
- Examine matches, delete all, skip all
- Action on [qMessagePattern:backtrace] ?
- Edit, delete, skip
- Action on [qMessagePattern:backtrace depth,separator] ?
- Edit, delete, skip
Attachments
For Gerrit Dashboard: QTQAINFRA-3529 | ||||||
---|---|---|---|---|---|---|
# | Subject | Branch | Project | Status | CR | V |
289430,4 | Handle blacklists where a test is specified multiple times | dev | qt/qtqa | Status: ABANDONED | 0 | 0 |
290061,2 | Fix infinite loop in blacklist tool if BLACKLIST file doesn't exist | master | qt/qtqa | Status: ABANDONED | 0 | 0 |