Timed-out testcases should be marked as SKIPPED, or FAILED
Bug #740911 reported by
Markus Korn
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Zeitgeist Framework |
Fix Released
|
Undecided
|
Siegfried Gevatter | ||
Bug Description
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 too.
Alternativly we should invest some time to find out why they time out and fix them.
Related branches
| Changed in zeitgeist: | |
| status: | New → Confirmed |
| Changed in zeitgeist: | |
| assignee: | nobody → Manish Sinha (मनीष सिन्हा) (manishsinha) |
Revision history for this message
| Siegfried Gevatter (rainct) wrote | #1 |
Revision history for this message
| Siegfried Gevatter (rainct) wrote | #2 |
| Changed in zeitgeist: | |
| assignee: | Manish Sinha (मनीष सिन्हा) (manishsinha) → Siegfried Gevatter (rainct) |
| milestone: | none → 0.8.0 |
| status: | Confirmed → Fix Released |
To post a comment you must log in.
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...