This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: GCC Buildbot
- From: Joseph Myers <joseph at codesourcery dot com>
- To: Paulo Matos <pmatos@linki.tools>
- Cc: <gcc at gcc dot gnu dot org>, Sergio Durigan Junior <sergiodj at redhat dot com>, <dje dot gcc at gmail dot com>
- Date: Wed, 20 Sep 2017 17:14:54 +0000
- Subject: Re: GCC Buildbot
- Authentication-results: sourceware.org; auth=none
- References: <fe9f8738-9edd-69a9-0161-6f8b24efdaa3@linki.tools>
On Wed, 20 Sep 2017, Paulo Matos wrote:
> - buildbot can notify people if the build fails or if there's a test
> regression. Notification can be sent to IRC and email for example. What
> would people prefer to have as the settings for notifications?
It's very useful if someone reviews regressions manually and files bugs /
notifies authors of patches that seem likely to have caused them / fixes
them if straightforward. However, that can take a lot of time (especially
if you're building a large number of configurations, and ideally there
would be at least compilation testing for every target architecture
supported by GCC if enough machine resources are available). (I do that
for my glibc bot, which does compilation-only testing for many
configurations, covering all supported glibc ABIs except Hurd - the
summaries of results go to libc-testresults, but the detailed logs that
show e.g. which test failed or failed to build aren't public; each build
cycle for the mainline bot produces about 3 GB of logs, which get deleted
after the following build cycle.)
--
Joseph S. Myers
joseph@codesourcery.com