Re-titling/componenting for the actual issue. Could also make this a phab bug about the fact that commit-sourced versions of DREVs lack the binary files, but I think it's likelier to be handled in Lando sooner if it's made to block landings when the current version of a DREV is sourced from a commit, than waiting for upstream Phab to fix.
(In reply to Emilio Cobos Álvarez (:emilio) from comment #2)
I did not resubmit it, because that revision was totally fine.
Then yeah, the empty binary files are expected. If you compare the last submitted DREV with the version created from the first landing you can see the issue. And the fact that that the first landing was fine.
(In reply to Kagami :saschanaz from comment #3)
https://phabricator.services.mozilla.com/D113359 is also affected, I wonder this is some kind of a regression?
Not a regression, this has always been the case as far as I know.
(In reply to Kagami :saschanaz from comment #4)
Resubmitting sometimes kills the images and sometimes restores them, as far as I can tell.
I'd be very surprised if resubmitting with moz-phab ever kills binary files, do you have an example you can link?
Component: moz-phab → Lando
Summary: moz-phab uploaded a binary file as empty, somehow → Lando allows re-landing committed versions of DREVs, which may result in empty binary files