Here is the regression range: Last good revision: 1ece26f610490b707948f20fe1230dbe306ef985 (2020-02-09) First bad revision: 813768d074e3accc36dc3313d0bffb658dcc562d (2020-02-10) Pushlog: https://hg.mozilla.org/mozilla-central/pushloghtml?fromchange=1ece26f610490b707948f20fe1230dbe306ef985&tochange=813768d074e3accc36dc3313d0bffb658dcc562d When bisecting it further I get this pushlog: https://hg.mozilla.org/mozilla-central/pushloghtml?fromchange=4c08723ed20aec9a60d09247ba7ff0ed2beb62aa&tochange=d3aa4a9e4dfd20e2be232a415a705a250aa17f63 and when switching to autoland I get this error: `ERROR: Unable to exploit the merge commit. Origin branch is mozilla-central, and the commit message for d3aa4a9e was: Update configs. IGNORE BROKEN CHANGESETS CLOSED TREE NO BUG a=release ba=release`
Bug 1640425 Comment 2 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
Here is the regression range made on Windows 10x64: Last good revision: 1ece26f610490b707948f20fe1230dbe306ef985 (2020-02-09) First bad revision: 813768d074e3accc36dc3313d0bffb658dcc562d (2020-02-10) Pushlog: https://hg.mozilla.org/mozilla-central/pushloghtml?fromchange=1ece26f610490b707948f20fe1230dbe306ef985&tochange=813768d074e3accc36dc3313d0bffb658dcc562d When bisecting it further I get this pushlog: https://hg.mozilla.org/mozilla-central/pushloghtml?fromchange=4c08723ed20aec9a60d09247ba7ff0ed2beb62aa&tochange=d3aa4a9e4dfd20e2be232a415a705a250aa17f63 and when switching to autoland I get this error: `ERROR: Unable to exploit the merge commit. Origin branch is mozilla-central, and the commit message for d3aa4a9e was: Update configs. IGNORE BROKEN CHANGESETS CLOSED TREE NO BUG a=release ba=release`