PTL taking too long to detect updated configuration

Description

PTL tests could run in much less time if changes in configuration were recognized by finding a line in the log files rather than searching for a line than never appears. Many instances of lines similar to the following appear in the PTL log:

2017-10-30 20:00:46,070 INFO scheduler swdev log match: searching for "Error reading line" - attempt 11

This causes delays of several seconds on nearly every test. Very annoying!

Acceptance Criteria

None

Assignee

Michael Karo

Reporter

Michael Karo

Severity

3-High

OS

None

Start Date

None

Pull Request URL

Story Points

1

Fix versions

Priority

High
Configure