Closed
Bug 1511733
Opened 7 years ago
Closed 6 years ago
mozregression does not work
Categories
(Testing :: mozregression, defect)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: alice0775, Assigned: Kwan)
Details
Attachments
(1 file)
|
49 bytes,
text/x-github-pull-request
|
Kwan
:
checked-in+
|
Details | Review |
Execute the following in command.prompt.
mozregression --app thunderbird --repo comm-central --good 1d9d688d566980be56ad1c86b805c5675f9412fa --bad 22fb120a634f0281b496b650d21da0d05bded5d4
Actual Results:
0:01.17 INFO: 22fb120a634f0281b496b650d21da0d05bded5d4 is not a release, assuming it's a hash...
0:01.92 INFO: 1d9d688d566980be56ad1c86b805c5675f9412fa is not a release, assuming it's a hash...
0:01.92 ERROR: Unable to bisect inbound for `thunderbird`
Expected results:
Should perform bisect
|
||
Comment 1•7 years ago
|
||
:( I don't know what's going on here offhand, bisecting thunderbird is definitely not something well-tested within mozregression. Would definitely accept/review a patch for this, but don't have time to look into this myself.
|
Assignee | |
Comment 2•6 years ago
|
||
This is happening because there is no ThunderbirdInboundConfigMixin, and using hashes forces checking integration. Of course after that one then runs into mozregression not knowing comm-central is a repo (bug 1510263).
Assignee: nobody → moz-ian
Status: NEW → ASSIGNED
|
|
Assignee | |
Comment 3•6 years ago
|
||
|
|
Assignee | |
Updated•6 years ago
|
Attachment #9058229 -
Flags: checked-in+
|
|
Assignee | |
Comment 4•6 years ago
|
||
Released in CLI 2.3.41 and GUI 0.9.39
Status: ASSIGNED → RESOLVED
Closed: 6 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•