On Sat, 2 May 2020, 10:02 Matthias Bläsing, <[email protected]> wrote:
> a) an external change causes test failures - the recent failure of the > vscode extension build is one such sample > b) an external outage causes test failures - neighther github, nor > apache apache gitbox, nor the ousol, nor maven central are perfect > c) travis changes infrastructure changes - I have seen this in other > projects > > I don't say travis should be ignored, but putting it on a pedastal is > also wrong. > Which part of what I said implies putting it on a pedastal?! It's a PITA! ;-) But it picks up problems, and is currently the thing we have. Of your scenarios, a) and c) require prioritising fixes before further PRs being merged, and b) means the RM has to be good at retriggering and reading the build logs! I also think in and out of freeze approaches to this could be different. Best wishes, Neil >
