From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 13142 invoked by alias); 28 Dec 2014 22:46:05 -0000 Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org Received: (qmail 13126 invoked by uid 89); 28 Dec 2014 22:46:03 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-3.0 required=5.0 tests=AWL,BAYES_00,SPF_HELO_PASS,SPF_PASS,T_RP_MATCHES_RCVD autolearn=ham version=3.3.2 X-HELO: mx1.redhat.com Received: from mx1.redhat.com (HELO mx1.redhat.com) (209.132.183.28) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with (AES256-GCM-SHA384 encrypted) ESMTPS; Sun, 28 Dec 2014 22:46:00 +0000 Received: from int-mx14.intmail.prod.int.phx2.redhat.com (int-mx14.intmail.prod.int.phx2.redhat.com [10.5.11.27]) by mx1.redhat.com (8.14.4/8.14.4) with ESMTP id sBSMjxnh031508 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=FAIL) for ; Sun, 28 Dec 2014 17:45:59 -0500 Received: from localhost (dhcp-10-15-16-169.yyz.redhat.com [10.15.16.169]) by int-mx14.intmail.prod.int.phx2.redhat.com (8.14.4/8.14.4) with ESMTP id sBSMjwET025993 (version=TLSv1/SSLv3 cipher=AES128-GCM-SHA256 bits=128 verify=NO) for ; Sun, 28 Dec 2014 17:45:59 -0500 From: Sergio Durigan Junior To: GDB Development Subject: Happy New BuildBot X-URL: http://blog.sergiodj.net Date: Sun, 28 Dec 2014 22:46:00 -0000 Message-ID: <87mw67jsux.fsf@redhat.com> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.3 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain X-IsSubscribed: yes X-SW-Source: 2014-12/txt/msg00052.txt.bz2 Hi there, After spending some weeks playing with, tweaking and (sometimes) fighting against BuildBot, I think I finally reached a state when I can talk about using it for our project in an "official" way. The purpose of our BuildBot is to build every commit made to the repository, test it, and check for regressions. Hopefully, it will help us catch them very quickly. First of all, I would like to thank Tom Tromey because he was the one who started to tackle this problem long ago, in 2011. To start my investigations, I used his previous work at . Although I had to change most of the master configuration file, the code to compare the test results is almost the same. Thanks, Tom! Now, the current configuration can be found at . I intend to submit it to gdb-patches when I have most of the bureaucracy figured out, and it will live in the gdb/contrib directory. I have also moved the old BuildBot page on our wiki (it is now called FeaturesForBuildBot), and I am currently using the BuildBot page to write about our yet-to-be-released BuildBot: . This page will be expanded when I have most of the bureaucracy figured out, as well. I'm talking to Frank in order to determine the best way to run our buildmaster. I'm not sure Sourceware's server is a good place, but we'll see. I expect to have this solved until mid-January. Unfortunately, right now I'm running our BuildBot inside Red Hat's network, so it's only accessible through VPN. Meanwhile, you guys can take a look at an existing BuildBot instance running for WebKit: Ours will look more or less like this. Our BuildBot will also send e-mails to gdb-testers every time it sees a regression. The e-mail will look like: Unfortunately, GDB's testsuite has some racy testcases that can pollute those logs; it will take some time until we filter them. And there is also an IRC bot that can be enabled, if people are interested. You might also want to start considering offering some buildslaves for our BuildBot, of course :-). Opinions and suggestions are welcome, modulo I don't plan to spend too much time implementing big things now. -- Sergio GPG key ID: 0x65FC5E36 Please send encrypted e-mail if possible http://sergiodj.net/