Closed
Bug 1241830
Opened 9 years ago
Closed 9 years ago
[GUI] stopping a bisection can be quite long
Categories
(Testing :: mozregression, defect)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: parkouss, Assigned: parkouss)
Details
Attachments
(1 file)
In the GUI we are basically waiting for threads to finish when we stop the bisection - so this can take some time, and this is not a problem since it is not blocking the ui anyway.
But in some cases, it can take a LONG time. For example, use a big range where there is no build, like 2005 to 2006, and click stop: the log will be polluted by a long list of warnings.
Let's improve that!
|
Assignee | |
Comment 1•9 years ago
|
||
|
||
Comment 2•9 years ago
|
||
Comment on attachment 8710949 [details] [review]
stop looking for mid build
Looks good! One minor suggestion/question in the PR, maybe I'm missing some context though.
Attachment #8710949 -
Flags: review?(wlachance) → review+
|
|
Assignee | |
Comment 3•9 years ago
|
||
Yup thanks, I slightly changed the code. :)
Landed in https://github.com/mozilla/mozregression/commit/647a8d4b230b97f146f081df72693ae22c582f05.
Status: ASSIGNED → RESOLVED
Closed: 9 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•