Closed Bug 751847 Opened 13 years ago Closed 13 years ago

A manifest file with every entry disabled is treated as if no manifest was specified

Categories

(Testing Graveyard :: Mozmill, defect)

Product:
Testing Graveyard
Component:
Mozmill
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED WONTFIX

People

(Reporter: davehunt, Unassigned)

References

Details

(Whiteboard: [mozmill-1.5.13-])

It appears that when a manifest file is provided for Mozmill 1.5.11 where every entry is disabled, Firefox launches and nothing else happens. This is the same behaviour as when no manifest/tests are specified, or when the manifest is empty. With the upcoming patch for bug 751143 we will have such a manifest file, and this will likely cause our testruns to stall.
Blocks: 751143
What about Mozmill 2? As I have mentioned on the other bug we are most likely don't want to fix it on the 1.5 branch.
This is fine for Mozmill 2, however this will potentially block us from moving skips to manifest files for Mozmill 1.5.
Whiteboard: [mozmill-1.5.12?]
Ah, I see. So yeah, good candidate why we probably need that. It shouldn't be that hard to fix, so I would be ok in having it fixed in 1.5. Clint, what's your opinion?
Whiteboard: [mozmill-1.5.12?] → [mozmill-1.5.13?]
Since we decided to just use the -t option in 1.5.x we aren't going to use manifests there. WONTFIXing.
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → WONTFIX
Whiteboard: [mozmill-1.5.13?] → [mozmill-1.5.13-]
Product: Testing → Testing Graveyard
You need to log in before you can comment on or make changes to this bug.