From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 69824 invoked by alias); 17 Jun 2015 17:27:34 -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 69808 invoked by uid 89); 17 Jun 2015 17:27:34 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-2.5 required=5.0 tests=BAYES_00,FREEMAIL_FROM,RCVD_IN_DNSWL_NONE,RP_MATCHES_RCVD,SPF_PASS autolearn=ham version=3.3.2 X-HELO: resqmta-po-02v.sys.comcast.net Received: from resqmta-po-02v.sys.comcast.net (HELO resqmta-po-02v.sys.comcast.net) (96.114.154.161) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with (AES128-SHA encrypted) ESMTPS; Wed, 17 Jun 2015 17:27:33 +0000 Received: from resomta-po-13v.sys.comcast.net ([96.114.154.237]) by resqmta-po-02v.sys.comcast.net with comcast id hVSt1q00457bBgG01VTX9j; Wed, 17 Jun 2015 17:27:31 +0000 Received: from [IPv6:2001:558:6045:a4:40c6:7199:cd03:b02d] ([IPv6:2001:558:6045:a4:40c6:7199:cd03:b02d]) by resomta-po-13v.sys.comcast.net with comcast id hVTW1q00Q2ztT3H01VTX70; Wed, 17 Jun 2015 17:27:31 +0000 From: Mike Stump Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable Subject: Crazy? Message-Id: <57BF10A2-F13E-4399-8D18-A662681F5384@comcast.net> Date: Wed, 17 Jun 2015 17:27:00 -0000 To: "gdb@sourceware.org" Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\)) X-SW-Source: 2015-06/txt/msg00039.txt.bz2 In remote.c we have: #define CRAZY_MAX_THREADS 1000 We need something that is either bigger, or obtainable from the target. If= bigger, I can just hack my sources to be different. If obtainable from th= e target, we=92ll I=92d let someone pick a q spelling for it and I could tr= y my hand at implementing it. Another solution is to just trust the target= and remove the limit altogether. I kinda like the last option. I can=92t= imagine a developer would ever be saved by the limit. So, would removal of the limit be reasonable? >From gdb-return-44435-listarch-gdb=sources.redhat.com@sourceware.org Wed Jun 17 18:09:39 2015 Return-Path: Delivered-To: listarch-gdb@sources.redhat.com Received: (qmail 53257 invoked by alias); 17 Jun 2015 18:09:38 -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 Delivered-To: mailing list gdb@sourceware.org Received: (qmail 53244 invoked by uid 89); 17 Jun 2015 18:09:38 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-0.8 required=5.0 tests=AWL,BAYES_50,RP_MATCHES_RCVD,SPF_PASS autolearn=ham version=3.3.2 X-HELO: kwanyin.sergiodj.net Received: from kwanyin.sergiodj.net (HELO kwanyin.sergiodj.net) (176.31.208.32) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with (AES128-SHA encrypted) ESMTPS; Wed, 17 Jun 2015 18:09:36 +0000 From: Sergio Durigan Junior To: GDB Subject: [BuildBot] News and announcements X-URL: http://blog.sergiodj.net Date: Wed, 17 Jun 2015 18:09:00 -0000 Message-ID: <87616mmcks.fsf@sergiodj.net> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.3 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain X-SW-Source: 2015-06/txt/msg00040.txt.bz2 Content-length: 4875 Hi there, It has been some time since I set our BuildBot instance at: And I figured I could send a message announcing some news here. New buildslaves =============== First of all, I would like to thank IBM again for the old POWER7 buildslaves by new, more capable POWER8 VM's. We now have one PPC64BE and one PPC64LE buildslaves, both running Fedora 22. Special thanks to Tulio Magno Quites Machado Filho and to Edjunior Machado, both from IBM Brazil, for all the help with the new VM's. Much appreciated! Now, we have the following buildslaves in our BuildBot: - One Fedora 21 x86_64 machine (owned by me; more expected to come in the next months) - One Fedora 22 PPC64BE machine (owned by Edjunior Machado) - One Fedora 22 PPC64LE machine (owned by Edjunior Machado) - One Fedora 21 s390x machine (owned by Mark Wielaard) - One Debian Wheezy x86_64 machine (owned by Mark Wielaard) - One Debian Wheezy i686 machine (owned by Mark Wielaard) (There are also 4 FreeBSD buildslaves, but they are currently inactive.) As I said, I expect to receive two more x86_64 machines in the next months; I intend to install Fedora in at least one of them, because the current Fedora x86_64 machine (owned by me) is struggling to keep the pace with the other buildslaves. I also tried to dedicate some time to put a buildslave on an AIX machine (in the GCC Farm). This was a request by David Edelsohn. However, I did not manage to compile GDB there, and after spending some time trying to figure out why, I had to switch context to another task. If you are able to help with this, I would really appreciate. Needless to say, we also welcome donations of new machines for our BuildBot! For example, we don't have an ARM buildslave yet, which would be very nice. So if you're interested in helping us, you can either take a look at this wiki page: Or contact me directly. The more machines we have, the more we can test GDB :-). New notifications ================= If you commit a piece of code that breaks GDB in any of the current builders, you will now receive a direct e-mail from BuildBot. This was an old feature I had in mind, and Mark Wielaard put some pressure to implement it :-). The way it is implemented today, you will receive a message for every builder that is not able to compile your code. This means that you can end up receiving lots of e-mails (currently, we have 24 builders). While I agree that this may be annoying, well, breaking GDB is also annoying, so consider this a punishment! Also, it is not uncommon to see commits that break only specific builders, so I think it is important to trigger a new notification every time something bad happens. I have also enabled a new notification for when a buildslave goes offline. I decided to do that after having problems with buildslaves that were unstable and required constant monitoring. Now, BuildBot automatically sends an e-mail to the buildslave's owner, notifying him. New builders ============ Pedro asked for a new builder to test just the compilation of the new --enable-build-with-cxx flag. It is now created on: This builder just compiles GDB, i.e., it does not run the testsuite like the others. Doug asked me if it was possible to create a new builder to test things with --target_board=stabs. Unfortunately, we don't have resources to create this builder on the x86_64 machines; I will try to create the builder on the PPC64 buildslaves and see how they behave. Problematic testcases ===================== Efforts on reducing the number of problematic testcases are being done, mostly by Pedro. Thanks, Pedro! Hopefully, sometime in the future we will reach a state when all the notifications of regressions will actually be trustworthy. And that's it. Just a remind, all the reports generated by the BuildBot are publicly accessible on the gdb-testers mailing list: This is now a very high-volume mailing list, so be aware if you decide to subscribe to it! Other than that, I am looking forward to improving the BuildBot in any way that the project needs (taking into consideration the amount of spare time I have, of course). My next steps are: - Try to fit the builder requested by Doug using the current resources - Update the existing x86_64 machine to Fedora 22 - Get the new x86_64 machines and set them up for our BuildBot - Get the AIX buildslave up and running - Continue trying to convince others to donate buildslaves to us :-) Any help is appreciated, of course. Cheers, -- Sergio GPG key ID: 237A 54B1 0287 28BF 00EF 31F4 D0EB 7628 65FC 5E36 Please send encrypted e-mail if possible http://sergiodj.net/