If you think a bug might affect users in the 57 release, please set the correct tracking and status flags for Release Management.

change check.py's -c option to detect stalled clientproxy state

RESOLVED FIXED

Status

Release Engineering
General
P3
normal
RESOLVED FIXED
6 years ago
4 years ago

People

(Reporter: bear, Assigned: bear)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: [android][tegra][sut_tools])

Attachments

(1 attachment)

(Assignee)

Description

6 years ago
now that our pool is much larger, the rate of stalled clientproxy daemons has increased.  A stalled CP shows up on the dashboard as:

tegra-059 	INACTIVE 	INACTIVE 	OFFLINE 	CP 0d 31299s;

Right now we don't detect this in check.py but this patch changes that.

if -c is passed and the above pattern is found, then check.py will stop all tegra daemons, reset the flags and restart the clientproxy daemon.
(Assignee)

Updated

6 years ago
Assignee: nobody → bear
Priority: -- → P3
Whiteboard: [android][tegra][sut_tools]
(Assignee)

Comment 1

6 years ago
Created attachment 590026 [details] [diff] [review]
change -c behaviour to check for stalled CP
Attachment #590026 - Flags: review?(hwine)
Comment on attachment 590026 [details] [diff] [review]
change -c behaviour to check for stalled CP

Review of attachment 590026 [details] [diff] [review]:
-----------------------------------------------------------------

per irc, remove 'logTD' test in new code, then good to go.
Attachment #590026 - Flags: review?(hwine) → review+
(Assignee)

Comment 3

6 years ago
Comment on attachment 590026 [details] [diff] [review]
change -c behaviour to check for stalled CP

https://hg.mozilla.org/build/tools/file/d96218e010e2
Attachment #590026 - Flags: checked-in+
(Assignee)

Comment 4

6 years ago
deployed to all production foopies
Status: NEW → RESOLVED
Last Resolved: 6 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.