Hi, Am Samstag, den 02.05.2020, 09:49 +0100 schrieb Neil C Smith: > If master testing is broken, that should be fixed before other > merges. If it's a flaky test, and we have a few, then it should be > retriggered to see if it passes.
I'm not a fan of "this is always right in all situations", these rules have the tendency to become religious. Some samples: 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. Greetings Matthias --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected] For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
