Closed Bug 636231 Opened 15 years ago Closed 14 years ago

clientproxy is not reacting to cleanup step errors properly

Categories

(Release Engineering :: General, defect)

Product:
Release Engineering
Component:
General
Platform:
ARM
Android
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED FIXED

People

(Reporter: bear, Assigned: bear)

References

Details

(Whiteboard: [android][tegra])

tegra-010 was failing in the cleanup step with this error: DeviceRoot None /builds/tegra-010/talos-data/../error.flg Remote Device Error: devRoot from devicemanager [None] is not correct and clientproxy did not see the error flag at all and allowed the buildslave to remain active, which then proceeded to chew thru build jobs at a high rate of FAIL
Assignee: nobody → bear
Blocks: 610600
Whiteboard: [android][tegra]
Fixed in other bugs.
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → FIXED
Product: mozilla.org → Release Engineering
You need to log in before you can comment on or make changes to this bug.