Closed
Bug 1422117
Opened 7 years ago
Closed 3 years ago
Crash during bissection process
Categories
(Testing :: mozregression, defect)
Testing
mozregression
Tracking
(Not tracked)
RESOLVED
DUPLICATE
of bug 1567259
People
(Reporter: guillaume-heritiana.sabatie, Unassigned)
Details
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:58.0) Gecko/20100101 Firefox/58.0
Build ID: 20171123161455
Steps to reproduce:
Processing a bissection.
platform: Windows-10-10.0.16299
python: 2.7.14 FROZEN (32bit)
mozregui: 0.9.17
mozregression: 2.3.21
message: IndexError: list index out of range
traceback: File ".\mozregui\bisection.py", line 72, in bisect_further
File "..\mozregression\bisector.py", line 585, in bisect
File "..\mozregression\build_range.py", line 293, in range_for_inbounds
File "..\mozregression\build_range.py", line 198, in check_expand
File "..\mozregression\build_range.py", line 238, in get_future
Actual results:
A crash
Expected results:
Processing Bissection
Comment 1•7 years ago
|
||
Could you provide information on what input you provided mozregression to get this result? (start/end dates, good/bad choices)
Without that I can't really do anything. :(
Flags: needinfo?(guillaume-heritiana.sabatie)
Reporter | ||
Comment 2•7 years ago
|
||
start date 11/7/2016
end date 30/10/2017
Only bad choices until the app crash. Can i find a log of the last launch ?
Flags: needinfo?(guillaume-heritiana.sabatie)
Comment 3•7 years ago
|
||
that's probably enough for me to go on, needinfo'ing myself as a reminder to look into this next week
Flags: needinfo?(wlachance)
Comment 4•7 years ago
|
||
Hmm, with that set of choices it just stops bisecting after getting to the range of 2016/11/17 - 2016/11/18, which is more or less what I'd expect.
Can you reproduce if you try again?
Flags: needinfo?(wlachance) → needinfo?(guillaume-heritiana.sabatie)
sounds to me like it's a duplicate of bug 1263358
Which is the bug, I'm currently experiencing.
It happens, when two dates are directly next to each other.
Regards,
Djfe
Comment 6•3 years ago
|
||
(In reply to Djfe from comment #5)
sounds to me like it's a duplicate of bug 1263358
... was marked a duplicate of Bug 1567259 - mozregression triggers "IndexError: list index out of range" - which has subsequently been fixed.
Status: UNCONFIRMED → RESOLVED
Closed: 3 years ago
Flags: needinfo?(guillaume-heritiana.sabatie)
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•