I have also lead in with two tests of type B and then it is B - good B - good A - bad
So it seems like the ones that want to evaluate the log for the raised "bad" can only go first and once. So it still could be that python no more re-loads the code at all and thereby no more triggered "bad". That leads it to continue and then come up with the "not found". -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1937173 Title: FTBFS breezy 3.2.1-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/breezy/+bug/1937173/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
