Allow 0 timeout
Bug #1178185 reported by
Javier Collado
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| UTAH |
Fix Released
|
Critical
|
Javier Collado | ||
Bug Description
After the schema update, a ts_control file is failing to validate because it
contains the following:
timeout: 0
the new schema doesn't allow this (only values greater than or equal to one);
but, since this breaks backwards compatibility, it will be updated to allow
this kind of setup.
Related branches
lp://qastaging/~javier.collado/utah/bug1178185
- Andy Doan (community): Approve
-
Diff: 155 lines (+24/-10) (has conflicts)7 files modifieddebian/changelog (+10/-0)
utah/client/runner.py (+1/-1)
utah/client/testcase.py (+1/-1)
utah/client/tests/test_runner.py (+3/-0)
utah/client/tests/test_testcase.py (+3/-0)
utah/client/tests/test_testsuite.py (+3/-5)
utah/client/testsuite.py (+3/-3)
- Andy Doan (community): Approve
-
Diff: 159 lines (+11/-54)7 files modifieddebian/changelog (+6/-0)
utah/client/runner.py (+1/-1)
utah/client/testcase.py (+1/-1)
utah/client/tests/test_runner.py (+0/-12)
utah/client/tests/test_testcase.py (+0/-26)
utah/client/tests/test_testsuite.py (+0/-11)
utah/client/testsuite.py (+3/-3)
| Changed in utah: | |
| assignee: | nobody → Javier Collado (javier.collado) |
| Changed in utah: | |
| status: | New → In Progress |
| importance: | Undecided → Critical |
| milestone: | none → 0.12.2 |
Revision history for this message
| Javier Collado (javier.collado) wrote | #1 |
| Changed in utah: | |
| status: | In Progress → Fix Committed |
| no longer affects: | utah/dev |
| Changed in utah: | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
An example of a log file for a job that has been affected by this problem is:
https:/