one phabricator revision not reopened as planned after it had landed got backed out from autoland
Categories
(Conduit :: Phabricator, defect)
Tracking
(Not tracked)
People
(Reporter: aryx, Unassigned)
Details
mkaply highlighted https://phabricator.services.mozilla.com/D164731 had landed and been backed out in bug 1791442 comment 10 but the phabricator revision did not get automatically reopened like it should have been.
|
||
Comment 1•3 years ago
|
||
This could be an import timing issue. Phabricator is possibly not sorting commits properly during import for the purposes of opening/closing revisions. Both the original commit and the reverting change were imported at 12:36 (ET) as part of the same import. The original commits were made about 30 minutes apart, with the backout being about 3 minutes before the import. This is just a quick guess, but this needs to be further investigated and an attempt to reproduce it should be made.
|
Reporter | |
Comment 2•3 years ago
|
||
If you need commits to check if this is related to both commits in the same import, let me know. Here is one https://phabricator.services.mozilla.com/D164226 (18 minutes between landing and backout).
|
||
Comment 3•3 years ago
|
||
I just had this on the stack here: https://phabricator.services.mozilla.com/D166198
They had landed at 11:02 UTC, the backout was at 11:41 UTC. Phabricator updated for the backout at 12:37 UTC, and the landing at 12:38 UTC.
This is the same for all 5 commits.
Description
•