The changes canonicalise request errors so same kind of errors are grouped together.
For example the following errors are same kind but they are treated different because the ip/port in the messages are different. As they are considered different errors, the test result overloaded with these repeated errors and it requires scrolling many pages to find other useful info.
read tcp 10.10.0.62:32774->63.35.24.107:443: read: connection reset by peer - 1
read tcp 10.10.0.62:43898->63.35.24.107:443: read: connection reset by peer - 1
read tcp 10.10.0.62:34816->63.35.24.107:443: read: connection reset by peer - 1
read tcp 10.10.0.62:43606->63.35.24.107:443: read: connection reset by peer - 1
read tcp 10.10.0.62:38474->63.35.24.107:443: read: connection reset by peer - 1
read tcp 10.10.0.62:33108->63.35.24.107:443: read: connection reset by peer - 1
read tcp 10.10.0.62:39948->63.35.24.107:443: read: connection reset by peer - 1
read tcp 10.10.0.62:43194->63.35.24.107:443: read: connection reset by peer - 1
read tcp 10.10.0.62:48982->63.35.24.107:443: read: connection reset by peer - 1
read tcp 10.10.0.62:57552->63.35.24.107:443: read: connection reset by peer - 1
The changes canonicalise request errors so same kind of errors are grouped together.
For example the following errors are same kind but they are treated different because the ip/port in the messages are different. As they are considered different errors, the test result overloaded with these repeated errors and it requires scrolling many pages to find other useful info.