Closed karlkfi closed 2 years ago
This turns out to be a bigger problem than I thought.
It turns out the Prune Success events are being sorted when they don't need to be, because they're (for now) consistently ordered by reverse apply order.
I'm going to have to fix the sorting algorithm again.
/retest
[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: karlkfi, mortent
The full list of commands accepted by this bot can be found here.
The pull request process is described here
Change the sorting algorithm to fix some flaky tests that became more frequent when client-side throttling was disabled.
With the current impl, only the WaitEvents have unpredictable ordering, reasoning is in comments in the sorting algorithm.