Closed Bug 621851 Opened 14 years ago Closed 13 years ago

Persisted object for update results not correctly build when failures occur

Categories

(Mozilla QA Graveyard :: Mozmill Tests, defect)

Product:
Mozilla QA Graveyard
Component:
Mozmill Tests
Type:
defect
Priority:
Not set
Severity:
major

Tracking

(Not tracked)

Status:
VERIFIED DUPLICATE of bug 705138

People

(Reporter: whimboo, Unassigned)

References

(
URL
)

Details

(Whiteboard: [mozmill-update])

Today I have discovered that in situations when a failure is raised in a test the teardownModule fails to setup the object for update results on the persisted object too. That shouldn't happen. It will need more investigation, so we know if it is our fault or if it is related to Mozmill itself. exception": { "message": "An active update is in the queue.", "exception": { "message": "persisted.updates[persisted.updateIndex] is undefined", Source: http://hg.mozilla.org/qa/mozmill-tests/file/43f2fb3d66b9/firefox/softwareUpdate/testDirectUpdate/test1.js
Is this still an issue Henrik?
Whiteboard: [mozmill-update]
Ups. I fixed that in bug 705138.
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → DUPLICATE
Status: RESOLVED → VERIFIED
Product: Mozilla QA → Mozilla QA Graveyard
You need to log in before you can comment on or make changes to this bug.