https://bz.apache.org/ooo/show_bug.cgi?id=127783
--- Comment #16 from [email protected] --- (In reply to Pedro from comment #15) > (In reply to damjan from comment #14) > > Windows does not crash in commit 2ed47956e3ec22116d5164494008afeac3f699a1 > > from 29 August 2015, suggesting a regression after that point in time. It > > would be helpful to bisect this bug and bug 127861 together. > > I'm available to help, but I have no idea what is bisecting and how to > bisect two bugs at the same time. As a marine biologist I'm more familiar > with dissecting :) You can't really bisect 2 bugs at the same time, but you can do multiple tests on each step of the bisect for 1 bug to reduce the number of steps for any other bugs. For example, using + to denote bug presence or - to denote bug absence, we knew both regressions happened between 2015 and 2018: Year 2015 2018 +-----------------------------------------------+ 127738- 127738+ 127861- 127861+ And after testing a commit in year 2017 and getting this result: Year 2015 2017 2018 +------------------------+----------------------+ 127738- 127738- 127738+ 127861- 127861- 127861+ I now know both regressions happened after that 2017 commit, so when I bisect bug 127861, I can start from 2017 instead of 2015, reducing the number of bisect steps. -- You are receiving this mail because: You are the assignee for the issue.
