Hi, On 2025-02-21 20:09:24 -0500, Robert Haas wrote: > In the case of my commit today, the failures are the result of a > 2-line regression diff with no functional impact that neither CI nor > any of the 11 reviewers noticed. That just shouldn't be the sort of > thing that results in somebody having to work evenings and weekends. > Perhaps if it DIDN'T result in a committer having to work evenings and > weekends, it wouldn't have taken 16 years for us to do something about > that problem.
I think you're right that it really depends on what the breakage is. If just about all animals die early in the test, it's more important the problem gets fixed more or the faulty commit(s) reverted. For one it prevents detecting other problems, as later, independent failures are hidden. For another it quite likely will affect other developers "at home", too. I'd also say that breaking CI and BF is probably something I'd consider more urgent, as that could indicate the commit was just generally less well tested. If, as the case here, a few animals fail with a minor regression.diffs output, one that doesn't indicate any major issue but just some corner case change in output, it's ok to leave it for the next day or so (*). Greetings, Andres Freund (*) With some adjustments based on circumstances. If the breakage is over a weekend, it's perhaps a bit less urgent. However, if it's the Friday before a feature freeze, it's obviously a differnt story.
