Apparently cb_timeout() is running in it's own world. Even if I create a
class variable, and change it inside cb_timeout, when I check it outside
the timeout afterwards it hasn't changed. Really weird...
You received this bug notification because you are a member of Zeitgeist
Framework Team, which is subscribed to Zeitgeist Framework.
Timed-out testcases should be marked as SKIPPED, or FAILED
Status in Zeitgeist Framework:
We do not know if the testcases which time out (I currently have towo of
them) really pass, so we should not mark them as such.
In newer versions of python we should use SKIP, but I guess FAILED is fine
Alternativly we should invest some time to find out why they time out and fix
Mailing list: https://launchpad.net/~zeitgeist
Post to : firstname.lastname@example.org
Unsubscribe : https://launchpad.net/~zeitgeist
More help : https://help.launchpad.net/ListHelp