2016-10-17
| ||
11:50 | • Ticket [3a3df6dc1f] megatest should not report COMPLETED/UNKNOWN status still Open with 3 other changes artifact: ddbe1158c4 user: tyardeni | |
11:49 | • Ticket [3a3df6dc1f]: 5 changes artifact: eed7959f2e user: tyardeni | |
11:49 | • New ticket [3a3df6dc1f]. artifact: e15577e480 user: tyardeni | |
Ticket Hash: | 3a3df6dc1fe756f0dc91c05762169d233706e2e6 | |||
Title: | megatest should not report COMPLETED/UNKNOWN | |||
Status: | Open | Type: | Feature_Request | |
Severity: | Critical | Priority: | Immediate | |
Subsystem: | Resolution: | Open | ||
Last Modified: | 2016-10-17 11:50:17 | |||
Version Found In: | 1.6104 | |||
Description: | ||||
Megatest is on occasion getting into the state/status COMPLETED/UNKNOWN | ||||
User Comments: | ||||
tyardeni added on 2016-10-17 17:49:30:
1. the state/status combiniation is invalid and should not occur 2. -rerun-clean handling in megatest.config cannot handle this combination correctly tyardeni added on 2016-10-17 17:50:17: Determined -rerun-clean behavior from valid-values config section: [validvalues] state start end completed status pass fail running n/a 0 1 2 cleanrerun-states KILLREQ,KILLED,UNKNOWN,INCOMPLETE,STUCK,NOT_STARTED cleanrerun-statuses FAIL,INCOMPLETE,ABORT,CHECK |