I think this was fixed inadvertently. I think we have at least one query in elastic-recheck that relies on a stack trace in tempest.txt for the failure and that has hits so this must be working.
I think this was fixed inadvertently. I think we have at least one query in elastic-recheck that relies on a stack trace in tempest.txt for the failure and that has hits so this must be working.