Closed Bug 1322926 Opened 8 years ago Closed 7 years ago

Excise the talos jobs that taskcluster tried to schedule on the stylo branch from the DB

Categories

(Release Engineering :: General, defect)

defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: philor, Assigned: nthomas)

References

Details

Bug 1311814 had taskcluster schedule talos jobs via buildbot-bridge, but failed to realize it would then schedule them on branches that had no builders for them from not having them enabled (for whatever reason, Ash only has talos-g4 enabled), and would schedule them on branches that don't exist in buildbot's world, Stylo.

Taskcluster giving up on the Ash jobs after 24 hours appears to have gotten rid of those, but according to https://secure.pub.build.mozilla.org/buildapi/pending we still have 576 pending jobs with names like "Ubuntu HW 12.04 x64 stylo talos g2-e10s" on the "Unknown" branch that are going to need DB surgery to get rid of.
Perhaps related, right at the time that taskcluster would have been giving up after 24 hours and cancelling them all, we started getting "buildbot-master82.bb.releng.scl3.mozilla.com:procs - buildbot-bridge is CRITICAL: PROCS CRITICAL: 2 processes with regex args /builds/bbb/bin/buildbot-bridge (http://m.mozilla.org/procs+-+buildbot-bridge)" alerts.
mysql> select id,buildername, complete, results from buildrequests where buildername like "% stylo %" and complete=0;
+-----------+------------------------------------------------+----------+---------+
| id        | buildername                                    | complete | results |
+-----------+------------------------------------------------+----------+---------+
| 134471357 | Ubuntu HW 12.04 x64 stylo talos chromez        |        0 |    NULL |
| 134471423 | Ubuntu HW 12.04 x64 stylo talos chromez        |        0 |    NULL |
...
| 134475139 | Ubuntu HW 12.04 x64 stylo talos tp5o-e10s      |        0 |    NULL |
| 134483637 | Ubuntu HW 12.04 x64 stylo talos tp5o-e10s      |        0 |    NULL |
+-----------+------------------------------------------------+----------+---------+
576 rows in set (0.02 sec)

mysql> update buildrequests set complete=1, results=2, complete_at=UNIX_TIMESTAMP() where buildername like "% stylo %" and complete=0;
Query OK, 576 rows affected (0.10 sec)
Rows matched: 576  Changed: 576  Warnings: 0
Assignee: nobody → nthomas
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → FIXED
Thanks for figuring out where those rogue jobs on Ash & Date came from too.
Component: General Automation → General
You need to log in before you can comment on or make changes to this bug.