Mir

Comment 4 for bug 1588929

Revision history for this message
Kevin DuBois (kdub) wrote :

I noticed this first during mir 0.23.0 release testing... so wanted to see if it was a the race was any better or worse with 0.23.0 vs 0.22.1.

So, did a quick manual check of time to failure on 0.23.0 and 0.22.1. (attached). Seems its just about as prevalent on each version of mir. This doesn't exonerate mir altogether, but IMO, should let us proceed with the 0.23.0 release.