[Lldb-commits] [PATCH] D98179: [lit] Sort test start times based on prior test timing data

nlopes added a comment. In D98179#2639565 , @davezarzycki wrote: > In D98179#2639554 , @nlopes wrote: > >> In D98179#2639491 , @davezarzycki >> wrote: >> >>> In D98179#2639

[Lldb-commits] [PATCH] D98179: [lit] Sort test start times based on prior test timing data

nlopes added a comment. In D98179#2639491 , @davezarzycki wrote: > In D98179#2639476 , @nlopes wrote: > >> Why are timeouts important? Our use case is running Alive2 with the test >> suite. Alive2 is heavy machine

[Lldb-commits] [PATCH] D98179: [lit] Sort test start times based on prior test timing data

nlopes added a comment. I'm talking about sorting just the summary of failed tests, not the whole output. We need the whole -vv output, but that can be out of order. Why are timeouts important? Our use case is running Alive2 with the test suite. Alive2 is heavy machinery and runs into timeouts.

[Lldb-commits] [PATCH] D98179: [lit] Sort test start times based on prior test timing data

nlopes added a comment. This patch makes the order of the list of failing tests non-deterministic. This is extremely annoying because you can't do a simple diff between test dumps anymore. Before the list of failed tests used to be sorted. Can we revert to the previous behavior please? The curr

[Lldb-commits] [PATCH] D98179: [lit] Sort test start times based on prior test timing data

nlopes added a comment. In D98179#2638801 , @mehdi_amini wrote: >> Can we revert to the previous behavior please? The current behavior is not >> user friendly. Thanks! > > To clarify: you care about the order in the final summary, not the actual > execut