Closed Bug 455734 Opened 17 years ago Closed 17 years ago

win32 talos tinderboxes reporting busted

Categories

(Release Engineering :: General, defect, P1)

Product:
Release Engineering
Component:
General
Platform:
All
Other
Type:
defect

Tracking

(Not tracked)

Status:
RESOLVED DUPLICATE of bug 455791

People

(Reporter: vlad, Assigned: anodelman)

Details

The win32 talos tinderboxes have all started reporting "previous cycle still running" -- not sure if something needs to be killed or what.
We also saw this yesterday - machines intermittently cycling orange with problems closing the browser after a given iteration of Ts. I've attempted simple reboots of the boxes but that doesn't seem to have any effect. I have a theory that the browser might be taking a little longer to close (due to some check in or another) and thus we occasionally throw a talos error when it assumes that the browser is unable to close at all. I'll try and look into this on talos stage to see if I can reproduce. There should be some way to get talos to wait longer for the browser to close after a given test has run - but, I also believe that these oranges are being caused by some change in the browser.
Assignee: server-ops → nobody
Component: Server Operations: Tinderbox Maintenance → Release Engineering: Maintenance
QA Contact: mrz → release
Component: Release Engineering: Maintenance → Release Engineering: Talos
Priority: -- → P1
Assignee: nobody → anodelman
Status: NEW → RESOLVED
Closed: 17 years ago
Resolution: --- → DUPLICATE
Component: Release Engineering: Talos → Release Engineering
Product: mozilla.org → Release Engineering
You need to log in before you can comment on or make changes to this bug.