Open rswarbrick opened 3 years ago
The milestone was wrong here: this is about hitting a specific coverage point (from when I went through a coverage report trying to work out what we were missing). Moving to V3 and removing from the M2 project.
We still don't hit this, of low concern as it really indicates buggy software so if it does something surprising it's not too bad. Still it'd be nice to test before M2.5
estimate range 2 - 4
Moving to M7 as this is part of V3 (targeted by that milestone, rather than M5)
This (obviously) causes an infinite loop, so will need something analogous to the loop warping support to let us stop again.