You're hitting a mozregression bug, I think. When I run mozregression, it gives me this fix-range first, which is the correct one: https://hg.mozilla.org/mozilla-central/pushloghtml?fromchange=49a271c42001f7bc5b9efadfc3e0b66dc0b67777&tochange=5caa044a10b8318931c12f5eb664f4b173243836 And then mozregression posts some warning-spew about failing-to-bisect further and then posting a warning because that failure somehow arrives at a single changeset being first-bad and also last-good, which it then represents as the single-changeset pushlog that you shared (notice no fromchange/tochange in that URL). Anyway -- in the correct push range, I think this would've been fixed by bug 1786147, probably (or perhaps bug 1789123).
Bug 1687372 Comment 7 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
You're hitting a mozregression bug, I think. When I run mozregression, it gives me this fix-range first, which is the correct one: https://hg.mozilla.org/mozilla-central/pushloghtml?fromchange=49a271c42001f7bc5b9efadfc3e0b66dc0b67777&tochange=5caa044a10b8318931c12f5eb664f4b173243836 And then mozregression posts some warning-spew about failing-to-bisect further and then posting a warning because that failure somehow arrives at a single changeset being first-bad and also last-good, which it then represents as the exact single-changeset pushlog that you shared (notice no fromchange/tochange in that URL in comment 6). Anyway -- in the correct push range, I think this would've been fixed by bug 1786147, probably (or perhaps bug 1789123).