Open Bug 1734717 Opened 3 years ago Updated 3 years ago

changeset c978b718d37e50e030b2d59dbe5da6e236afb9b7 on autoland is missing pushlog information

Categories

(Developer Services :: Mercurial: Pushlog, defect)

Product:
Developer Services
Component:
Mercurial: Pushlog
Type:
defect

Tracking

(Not tracked)

People

(Reporter: sheehan, Assigned: sheehan)

References

Details

Looks like this changeset landed without pushlog info. As of right now it is causing the unifyrepo daemon on hgmo to stall, meaning mozilla-unified is behind and Phabricator revisions aren't closing after landing.

I spoke with Mitch and neither of us could think of a good reason why doctoring the pushlog entry for the push that contains the parent changeset to also include c978b718d37e50e030b2d59dbe5da6e236afb9b7 would be a bad idea.

I ran insert into changesets (pushid, rev, node) values (151026, 595058, 'c978b718d37e50e030b2d59dbe5da6e236afb9b7'); on the hgssh copy of autoland's pushlog and now the unification process is running again.

The pushlog data isn't propagating to hgweb, so we may need to manually doctor those pushlogs as well.

Regressions: 1734715
You need to log in before you can comment on or make changes to this bug.