Closed Bug 652032 Opened 9 years ago Closed 9 years ago

possible race condition in sut_tools/reboot.py helper script during tp4m tests

Categories

(Release Engineering :: General, defect)

ARM
Android
defect
Not set

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: bear, Assigned: aki)

Details

(Whiteboard: [android][tegra])

Attachments

(1 file)

aki discovered that during the reboot step of a tp4m run the test is showing as failed even tho the test was run successfully.

after looking at it we found that clientproxy is shutting down the slave during the reboot step because it receives the "rebooting" signal from the tegra *but* before the slave shutsdown itself.

not sure what the core issue is but we are adding a proxy.flg semaphore to the reboot.py code to cause clientproxy to ignore that reboot signal until we can figure it out
Assignee: nobody → bear
Whiteboard: [android][tegra]
testing on staging now
Attachment #527709 - Flags: review?(aki)
Attachment #527709 - Flags: review?(aki) → review+
Comment on attachment 527709 [details] [diff] [review]
add proxy.flg to reboot step as workaround

committed changeset 1375:bf0c06bd1065
Attachment #527709 - Flags: checked-in+
assigning to aki so we remember to check staging and move this to production if ok
Assignee: bear → aki
Updated the various foopys with this after seeing various other intermittent reds in production.
Status: NEW → RESOLVED
Closed: 9 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.