Closed Bug 1490407 Opened 6 years ago Closed 6 years ago

Cannot reland backouted patches series

Categories

(Conduit :: Lando, defect)

defect
Not set
normal

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 1489126

People

(Reporter: TYLin, Unassigned)

References

Details

I'd like to reland patch series D5474 [1], and had reopened the revision and all the revisions it depends on. But the button is "Landing Blocked". 

D5474 [2] is ok to be relanded though.

[1] https://lando.services.mozilla.com/D5474/
[2] https://lando.services.mozilla.com/revisions/D5474/14287/
This is partly a duplicate of Bug 1489126, but it also appears that lando, in that the parent revisions are blocked because of missing author information. But I'm only seeing single revision on the stacked landing page, when I would expect to see all 4 revisions in that stack.
(In reply to Ting-Yu Lin [:TYLin] (UTC-7) from comment #0)
> D5474 [2] is ok to be relanded though.

This is incorrect, clicking "Re-Land D5474: Preview Landing" would show you:
> Landing Blockers:
>  - This diff does not have the proper author information uploaded to Phabricator. This can happen if the diff was created using the web UI, or a non standard client. The author should re-upload the diff to Phabricator using the "arc diff" command. 
> - This revision depends on the following revision which is still open: D5472 


(In reply to Tom Prince [:tomprince] from comment #1)
> This is partly a duplicate of Bug 1489126, but it also appears that lando,
> in that the parent revisions are blocked because of missing author
> information. But I'm only seeing single revision on the stacked landing
> page, when I would expect to see all 4 revisions in that stack.

To avoid needing to special case this, or have code which can display an arbitrary DAG of parents, if a revision is not landable we only show it and the blocker. The next iteration of this UI coming in Bug 1490337 will always display the full graph.
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.