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

Clean the schedulers for Android x86 before enabling everywhere

RESOLVED WORKSFORME

Status

Release Engineering
Platform Support
RESOLVED WORKSFORME
4 years ago
4 years ago

People

(Reporter: armenzg, Assigned: armenzg)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

Comment hidden (empty)
(Assignee)

Comment 1

4 years ago
I hope that these are the instructions:
https://wiki.mozilla.org/ReleaseEngineering/How_To/Fix_a_hung_scheduler_master
(Assignee)

Updated

4 years ago
Blocks: 960674
(Assignee)

Comment 2

4 years ago
Time to deal with this before we can tackle bug 960674.
Assignee: nobody → armenzg
(Assignee)

Comment 3

4 years ago
It seems that we have a process that cleans old schedulers every week:
mysql> select name from schedulers where name like '%vm_android%';
+---------------------------------------+
| name                                  |
+---------------------------------------+
| tests-ash-vm_android_2_3-opt-unittest |
+---------------------------------------+
1 row in set (0.01 sec)
Status: NEW → RESOLVED
Last Resolved: 4 years ago
Resolution: --- → WORKSFORME
(Assignee)

Comment 4

4 years ago
It seems that I had searched for the wrong scheduler:
mysql> select name from schedulers where name like '%ubuntu64_hw%';
+--------------------------------------+
| name                                 |
+--------------------------------------+
| tests-ash-ubuntu64_hw-opt-unittest   |
| tests-cedar-ubuntu64_hw-opt-unittest |
| tests-pine-ubuntu64_hw-opt-unittest  |
+--------------------------------------+
3 rows in set (0.11 sec)
That was bug 617017 (initially), and bug 755012 (specifically for schedulers).
(Assignee)

Comment 6

4 years ago
Thanks Nick!
You need to log in before you can comment on or make changes to this bug.