Closed arvoelke closed 4 years ago
While this is definitely a bug, since it only affects the test suite (and only in a pretty particular case) it's so far down the priority queue that, if we're being honest, it probably won't be worked on/fixed any time soon. So closing to reflect the fact that we have no plans to fix this (while acknowledging that it should be fixed in an ideal world 😉).
To reproduce, run:
It also happens with
--log-level=WARNING
, but it does not happen withlog-level=DEBUG
. The problem something to do with the way in which the test attempts to capture logging information at a particular level.