@Xinwei has described that this issue was found while running a larger test suite.
It only occurs sporadically, and is quite hard to reproduce.
He has only seen it approximately once or twice in a month, although it's not clear how many times the test suite was run during that time.
@Xinwei has described that this issue was found while running a larger test suite.
It only occurs sporadically, and is quite hard to reproduce.
He has only seen it approximately once or twice in a month, although it's not clear how many times the test suite was run during that time.