3 ms·
I take your point, but that assumes someone working 24 hour days, or constantly handing off the project to at least 2 other people every day. I don't think tho
by wccrawford 2y ago
I take your point, but that assumes someone working 24 hour days, or constantly handing off the project to at least 2 other people every day.
I don't think those are reasonable work scenarios, so it's more like 2 bisects (maybe 3!) per day, rather than 6.
- jsnell 2y agoNot really, it just assumes that the bisection process is automated. But also, I addressed exactly this objection in the second paragraph :)
- yencabulator 2y agoBisection and testing might be automated, but resolving merge conflicts isn't.
- jonhohle 2y agoIf a bisection takes a day, it would probably take longer to automate than just find it manually. For performance bugs, you may need to look at non-standard metrics or profiling that would otherwise be a one-off and don’t necessarily make sense to automate.
- jsnell 2y agoThe full bisection taking just a day doesn't seem compatible with the parameters of the story. Three weeks of FreeBSD changes seems to be about 500 commits. That's about 9 bisection steps. At two steps / day (the best you can do without automation), that's a full work week. It seems obvious that this is worth automating.