search for: 10hs

...e actively working on that (minus sleep time, etc). Since we're talking about an order of magnitude slower to debug, sleep time becomes a much bigger issue. If a hard problem takes about 5 hours on fast hardware, it can take up to 50 hours, and in that case, no one can work that long. If you do 10hs straight every day, it's still a week past. In agreement? I'll continue later, once we're in agreement over the base facts. cheers, --renato

...(minus sleep time, etc). Since we're talking about an order of >> magnitude slower to debug, sleep time becomes a much bigger issue. If >> a hard problem takes about 5 hours on fast hardware, it can take up to >> 50 hours, and in that case, no one can work that long. If you do 10hs >> straight every day, it's still a week past. > > > Sure - some issues take a while to investigate. No doubt - but so long as > the issue is live (be it flaky or consistent) it's unhelpful (moreso if it's > flaky, given the way our buildbots send mail - though I st...

Hi David, I think we're repeating ourselves here, so I'll reduce to the bare minimum before replying. On 6 October 2015 at 21:40, David Blaikie <dblaikie at gmail.com> wrote: > When I suggest someone disable notifications from a bot it's because those > notifications aren't actionable to those receiving them. This is a very limited view of the utility of buildbots.