Closed Bug 1360081 Opened 8 years ago Closed 8 years ago

mozregression would not narrow down autoland and inbound automatically, it seems only retrieve mozilla-cental.

Categories

(Testing :: mozregression, defect)

Product:
Testing
Component:
mozregression
Platform:
x86_64
Linux
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED WONTFIX

People

(Reporter: alice0775, Assigned: wlach)

References

Details

When I try get regression window of https://bugzilla.mozilla.org/show_bug.cgi?id=1358926#c12 However, mozregression would not narrow down autoland and inbound automatically, it seems only retrieve mozilla-cental. And also, I want to download specific autoland build from archive, but fails the following error. Steps to reproduce: Open http://archive.mozilla.org/pub/firefox/tinderbox-builds/autoland-linux64/ http://archive.mozilla.org/pub/firefox/tinderbox-builds/mozilla-inbound-linux64/ ERROR The request could not be satisfied. CloudFront attempted to establish a connection with the origin, but either the attempt failed or the origin closed the connection. Generated by cloudfront (CloudFront) Request ID: unekI4eHE14JhUaJUdrMqjy8AdeRr9jG_J-a5bVlI-Oafbxstb9h8g== ERROR The request could not be satisfied. CloudFront attempted to establish a connection with the origin, but either the attempt failed or the origin closed the connection. Generated by cloudfront (CloudFront) Request ID: w3biV9TK4Kou9ka49e_auwkhAkXmdNfluITZQEy-Hhk7vJvTdkX9BQ== I request that * improve mozregression tool to narrowing down automatically inbound/autoland * OR, provide archive http://archive.mozilla.org/pub/firefox/tinderbox-builds/autoland-linux64/ http://archive.mozilla.org/pub/firefox/tinderbox-builds/mozilla-inbound-linux64/
I think this is related to bug 1344936. Fortunately this only affects Linux right now, but we should figure this out.
Depends on: 1344936
I believe mozregression already supports using the taskcluster index for some things, so this might just be a matter of changing the logic somewhere... I guess I'll take this one, this isn't the first time I've heard people having trouble coming up with decent regression ranges.
Assignee: nobody → wlachance
Newsgroup thread about archive.mozilla.org and tinderbox builds: https://groups.google.com/d/msg/mozilla.dev.platform/r1J4b496XiM/42RpNfPnAwAJ
Hi Alice, I just tried to do a bisection today and it seems like the latest version of mozregression is using taskcluster as expected. What version of mozregression are you running? You can get that information by running: mozregression --version If it's lower than 2.3.11, you should upgrade. If you're getting this behaviour with the current version, not sure what's going on.
Flags: needinfo?(alice0775)
it was 2.3.10 when I file bug. And it was updated. And no error. But now, sudo apt-get install python-pip sudo pip2 install -U mozregression it is 2.3.11 And I try with 2.3.11 with final results of 2.3.10. mozregression --good 671a2f8542cadcf9aad318ab76250a730a03b240 --bad ac3275723df59db0f09198fdb61b51e7002c391a ********** You should use a config file. Please use the --write-config command line flag to help you create one. ********** 0:00.53 INFO: ac3275723df59db0f09198fdb61b51e7002c391a is not a release, assuming it's a hash... 0:00.53 INFO: 671a2f8542cadcf9aad318ab76250a730a03b240 is not a release, assuming it's a hash... 0:00.53 INFO: Getting mozilla-inbound builds between 671a2f8542cadcf9aad318ab76250a730a03b240 and ac3275723df59db0f09198fdb61b51e7002c391a 0:01.85 ERROR: The url 'https://hg.mozilla.org/integration/mozilla-inbound/json-pushes?fromchange=671a2f8542cadcf9aad318ab76250a730a03b240&tochange=ac3275723df59db0f09198fdb61b51e7002c391a' contains no pushlog. Maybe use another range ? fails with an error.
Flags: needinfo?(alice0775)
(In reply to Alice0775 White from comment #5) > it was 2.3.10 when I file bug. And it was updated. > And no error. > > But now, > sudo apt-get install python-pip > sudo pip2 install -U mozregression > > it is 2.3.11 > > And I try with 2.3.11 with final results of 2.3.10. > > mozregression --good 671a2f8542cadcf9aad318ab76250a730a03b240 --bad > ac3275723df59db0f09198fdb61b51e7002c391a > ********** > You should use a config file. Please use the --write-config command line > flag to help you create one. > ********** > > 0:00.53 INFO: ac3275723df59db0f09198fdb61b51e7002c391a is not a release, > assuming it's a hash... > 0:00.53 INFO: 671a2f8542cadcf9aad318ab76250a730a03b240 is not a release, > assuming it's a hash... > 0:00.53 INFO: Getting mozilla-inbound builds between > 671a2f8542cadcf9aad318ab76250a730a03b240 and > ac3275723df59db0f09198fdb61b51e7002c391a > 0:01.85 ERROR: The url > 'https://hg.mozilla.org/integration/mozilla-inbound/json- > pushes?fromchange=671a2f8542cadcf9aad318ab76250a730a03b240&tochange=ac3275723 > df59db0f09198fdb61b51e7002c391a' contains no pushlog. Maybe use another > range ? > > fails with an error. There don't seem to be any intermediary revisions inside that pushlog range: https://hg.mozilla.org/integration/mozilla-inbound/pushloghtml?fromchange=671a2f8542cadcf9aad318ab76250a730a03b240&tochange=ac3275723df59db0f09198fdb61b51e7002c391a I don't think that is an error, maybe the wording could be slightly more clear but AFAICT there isn't anything more mozregression can do.
So, mozregression cannot retrieve inside mozilla-inbound from following mozilla-central https://hg.mozilla.org/mozilla-central/pushloghtml?fromchange=671a2f8542cadcf9aad318ab76250a730a03b240&tochange=ac3275723df59db0f09198fdb61b51e7002c391a But, Manually I found inbound range. https://hg.mozilla.org/integration/mozilla-inbound/pushloghtml?fromchange=e8b32aaa2eec84c15f44cfd677142a0047481152&tochange=f3ccf0f50160e169389aa26a2d95ec225effcd3b Anyway, it seems an edge case, I imagine. I mark this WONTFIX.
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → WONTFIX
(In reply to Alice0775 White from comment #7) > So, mozregression cannot retrieve inside mozilla-inbound from following > mozilla-central > https://hg.mozilla.org/mozilla-central/ > pushloghtml?fromchange=671a2f8542cadcf9aad318ab76250a730a03b240&tochange=ac32 > 75723df59db0f09198fdb61b51e7002c391a Right, the pushlog range for mozilla-inbound is going to be different than for mozilla-central though. I'm not too surprised you got a result for the latter. I would say that you could run mozregression like this: https://hg.mozilla.org/mozilla-central/pushloghtml?fromchange=671a2f8542cadcf9aad318ab76250a730a03b240&tochange=ac3275723df59db0f09198fdb61b51e7002c391a ... but that doesn't seem to work either, because there's no commit message in that range that would tell you to bisect further into inbound or autoland. Anyway, I agree this is likely an edge case. Probably not worth investigating further. Thanks for filing the bug though!
You need to log in before you can comment on or make changes to this bug.