Closed devinrsmith closed 1 year ago
I've done 8 CI runs and so far have been unable to reproduce this issue. After #4802 merges, if this issues triggers in CI again we should have much more details to go off of.
I think #4802 fixes this - leaving open for a week to see if we here anymore cases.
Updated comment to specifically make sure this is about the timeout nature of this issue.
It appears that the following test is sometimes failing:
It suggests that there is an underlying race (potentially Batch / ETCR or related), or client implementation bug; but it's possible the timeout is too short given CI resources, TBD.