Disable notifiations on broken workers
Hi,
I propose to disable email and IRC notifications on workers which were never green (tests always failed): https://github.com/python/buildmaster-config/pull/86
- Alpine Linux
- Cygwin
- "AMD64 Clang UBSan 3." (3.6, 3.7 and 3.x, surprisingly, 2.7 is green)
Does anyone have a good reason to keep notifications for these workers?
I proposed this change because the Cygwin sent 2 emails in 2 days, whereas this worker is failing since it has been registered.
Victor
Night gathers, and now my watch begins. It shall not end until my death.
On Wed, Apr 10, 2019 at 4:08 PM Victor Stinner <vstinner@redhat.com> wrote:
Hi,
I propose to disable email and IRC notifications on workers which were never green (tests always failed): https://github.com/python/buildmaster-config/pull/86
- Alpine Linux
- Cygwin
- "AMD64 Clang UBSan 3." (3.6, 3.7 and 3.x, surprisingly, 2.7 is green)
Does anyone have a good reason to keep notifications for these workers?
Agreed. Lets not notify about intentionally unstable workers until we are happy that they can only report regressions. I can speak for the ubsan bots - the output on stderr regardless of tests passing is of interest to anyone looking at sanitizers (which is likely why 2.7 is green - there are still things that could be looked into on stderr). tests passing and failing ideally wouldn't happen but it looks like there is one test tripped up by the sanitizer (test_venv) for now.
I proposed this change because the Cygwin sent 2 emails in 2 days, whereas this worker is failing since it has been registered.
Victor
Night gathers, and now my watch begins. It shall not end until my death.
Python-Buildbots mailing list Python-Buildbots@python.org https://mail.python.org/mailman/listinfo/python-buildbots
Ok, I deployed the new configuration.
Victor
Le jeu. 11 avr. 2019 à 02:23, Gregory P. Smith <greg@krypto.org> a écrit :
On Wed, Apr 10, 2019 at 4:08 PM Victor Stinner <vstinner@redhat.com> wrote:
Hi,
I propose to disable email and IRC notifications on workers which were never green (tests always failed): https://github.com/python/buildmaster-config/pull/86
- Alpine Linux
- Cygwin
- "AMD64 Clang UBSan 3." (3.6, 3.7 and 3.x, surprisingly, 2.7 is green)
Does anyone have a good reason to keep notifications for these workers?
Agreed. Lets not notify about intentionally unstable workers until we are happy that they can only report regressions. I can speak for the ubsan bots - the output on stderr regardless of tests passing is of interest to anyone looking at sanitizers (which is likely why 2.7 is green - there are still things that could be looked into on stderr). tests passing and failing ideally wouldn't happen but it looks like there is one test tripped up by the sanitizer (test_venv) for now.
I proposed this change because the Cygwin sent 2 emails in 2 days, whereas this worker is failing since it has been registered.
Victor
Night gathers, and now my watch begins. It shall not end until my death.
Python-Buildbots mailing list Python-Buildbots@python.org https://mail.python.org/mailman/listinfo/python-buildbots
-- Night gathers, and now my watch begins. It shall not end until my death.
participants (2)
-
Gregory P. Smith -
Victor Stinner