[loganalyzer] Enhance Loganalyzer Fixture With Custom Regex#1797
Conversation
Loganalyzer has build int regex to match log files against. Some test cases while appropriately disabling some services, they fail loganalyzer scrutiny if it happend to match one of those regex's. This PR add ability for individual test cases to manipulate loganalyzer regex's. signed-of-by: Tamer Ahmed <[email protected]>
|
I do not understand this change. I think the existing code correctly loads the built in list if there is no disable_loganalyzer present in the testcases. If a testcase needs to manipulate the loganalyzer regex, there is an option to do so in loganalyzer.py.. (ignore_regex, expect_regex, match_regexp) |
There is another PR that make user of this change. The point is to have the step that loads the regex's before yield in the object such that test cases can add/remove to/from these regex. |
|
Discussed offline, Tamer will put in another PR to init the loganalyzer only if its not disabled |
#### Why I did it Update submodule pointer for swss to include recent changes 4f1d726 [portsorch] fix errors when moving port from one lag to another. (sonic-net#1797) ae44701 [orchagent] Put port configuration to APPL_DB according to autoneg mode (sonic-net#1769) 5295f91 Add failure handling for SAI get operations (sonic-net#1768) 7c7c451 Revert recirc port change (sonic-net#1813) 5528ebf Cleanup code (sonic-net#1814)
sonic-swss 29a0483 Cache routes for single nexthop for faster retrieval (sonic-net#1922) sonic-utilities 9bc6500 Modified the 'show ipv6 link-local-mode' command to display all interfaces by default (sonic-net#1797)
Description of PR
Summary:
Loganalyzer has build int regex to match log files against. Some
test cases while appropriately disabling some services, they fail
loganalyzer scrutiny if it happens to match one of those regex's.
This PR add ability for individual test cases to manipulate
loganalyzer regex's.
signed-of-by: Tamer Ahmed [email protected]
Fixes # (issue)
Type of change
Approach
What is the motivation for this PR?
How did you do it?
How did you verify/test it?
Any platform specific information?
Supported testbed topology if it's a new test case?
Documentation