It's not possible to define a time out per test
Bug #1408374 reported by
Leo Arias
on 2015-01-07
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| | Autopilot |
Undecided
|
Unassigned | ||
Bug Description
With the timeout argument of the autopilot run command we can define a timeout for each test in the suite, but it will be the same for all tests. Some tests take a lot longer than others, so it would be good to be able to define a time out in the test. If both timeouts are set, autopilot should use the minimum.
| Thomi Richards (thomir) wrote : | #1 |
| Leo Arias (elopio) wrote : | #2 |
um, yes. Sure it will work.
we set a timeout high enough for all tests, and then use the fixture timeout to put a smaller limit to smaller tests.
| Changed in autopilot: | |
| status: | New → Invalid |
To post a comment you must log in.
Surely you can already do this, with the Timeout fixture?