http://build.mozilla.org/builds/builds-4hr.js.gz is completely empty, and as a result no completed jobs are shown on tbpl. Condition for reopening the tree (after the last premature reopening): The tip push on https://tbpl.mozilla.org/?tree=Mozilla-Inbound must show every single job which runs and is visible for both Android XUL and Android in a completed state (orange, fine, but not purple or red from not actually running). No "I think it probably will" or "that might have fixed it." Every single job, in a completed state.
Typed this so many times lately, I forgot to type it again: mozilla-inbound, mozilla-central, mozilla-aurora and mozilla-beta are closed.
I'm seeing this in some logs: sqlalchemy.exc.InternalError: (InternalError) (144, "Table './buildbot/properties' is marked as crashed and last (automatic?) repair failed") 'DESCRIBE `properties`' () Can we repair that table?
per irc w/catlee, this is fallout from the DB outage earlier.
txt'd sheeri as she requested in irc earlier this evening.
Running table repair on properties now
buildbot.properties table successfully repaired, select queries against each against ran without error. The table was heavily fragmented. Prior to repair the index file on disk was 1018M, after repair it is 706M.
confirmed that the updater log is no longer showing an error
see bug 712988 as this is still happening.
(In reply to Matt Pressman [:mpressman] from comment #6) > buildbot.properties table successfully repaired, select queries against each > against ran without error. > > The table was heavily fragmented. Prior to repair the index file on disk was > 1018M, after repair it is 706M. Thanks Matt!
4 years ago