Closed Bug 1737504 Opened 3 years ago Closed 3 years ago

Phabricator thinks my changes were backedout a 2nd time

Categories

(Conduit :: Phabricator, defect)

Product:
Conduit
Component:
Phabricator
Type:
defect

Tracking

(Not tracked)

Status:
RESOLVED FIXED

People

(Reporter: pbone, Unassigned)

References

Details

The phabricator pages:
https://phabricator.services.mozilla.com/D122556

And bugzilla pages:
https://bugzilla.mozilla.org/show_bug.cgi?id=1725539

Appear to be out of sync. It looks like phabricator has picked up on the 1st backout a 2nd time and decided my patches are backed out again. But I'm fairly sure they're still in the tree.

  1. This shouldn't happen?
  2. Do I need to close these patches or would a phabricator admin prefer to to it (so they do it correctly as landed).

Thanks.

This appears to be another elm related issue:
ctuns added a reverting change: rMOZILLACENTRAL594dee35414f: Backed out 4 changesets (bug 1725539) for performance & crash regressions..Wed, Oct 13, 5:02 PM
ctuns added a reverting change: rELM594dee35414f: Backed out 4 changesets (bug 1725539) for performance & crash regressions..Sat, Oct 23, 3:19 AM

Component: Phabricator Integration → Phabricator
Flags: needinfo?(zeid)
Product: bugzilla.mozilla.org → Conduit

It appears this revision was affected before bug 1735361 was fixed. I believe because of that, the reverting commit across repos affected this revision. I could try and remove the related commit via "Edit Related Objects" -> "Edit Commits" dialog, which might help prevent future interference (https://phabricator.services.mozilla.com/rELMb31d0c7c8f5e651fd8d3bdc3ac62d4b4f41c31d0).

Flags: needinfo?(zeid)

Closing this bug since the fix in Comment 2 appears to have resolved the issue.

Status: NEW → RESOLVED
Closed: 3 years ago
Resolution: --- → FIXED
Depends on: 1729988
You need to log in before you can comment on or make changes to this bug.