On 07/20/2018 03:32 PM, Nishanth Aravamudan wrote:
On 20.07.2018 [15:11:14 -0400], Farhan Ali wrote:
I am seeing another issue pop up, in a different test. Even though it's a
different assertion, it might be related based on the call trace.
Just to be clear, this does not happen if you revert the original patch
(i.e., the one you bisected to before)?
I'm digging into the code now.
-Nish
I had not seen this issue before. I just ran my regression tests with
your fix and saw the failure in one of my test. The patch in itself
fixes the original issue I reported. I am going to try and debug some more.
Thanks
Farhan
