From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 120582 invoked by alias); 15 Sep 2015 15:22:56 -0000 Mailing-List: contact crossgcc-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: crossgcc-owner@sourceware.org Received: (qmail 120570 invoked by uid 89); 15 Sep 2015 15:22:55 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-1.4 required=5.0 tests=AWL,BAYES_00,FREEMAIL_FROM,RCVD_IN_DNSWL_LOW,SPF_PASS autolearn=ham version=3.3.2 X-HELO: mail-wi0-f175.google.com Received: from mail-wi0-f175.google.com (HELO mail-wi0-f175.google.com) (209.85.212.175) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with (AES128-GCM-SHA256 encrypted) ESMTPS; Tue, 15 Sep 2015 15:22:54 +0000 Received: by wicge5 with SMTP id ge5so34123466wic.0 for ; Tue, 15 Sep 2015 08:22:51 -0700 (PDT) X-Received: by 10.180.92.225 with SMTP id cp1mr8468614wib.2.1442330571101; Tue, 15 Sep 2015 08:22:51 -0700 (PDT) MIME-Version: 1.0 Received: by 10.194.121.10 with HTTP; Tue, 15 Sep 2015 08:22:31 -0700 (PDT) In-Reply-To: <55F82DB2.80306@gmail.com> References: <20150912200305.69b80a14@free-electrons.com> <55F60487.5030805@anw.at> <55F6081F.8070905@anw.at> <55F61553.6040401@anw.at> <55F82DB2.80306@gmail.com> From: Jean-Marie Lemetayer Date: Tue, 15 Sep 2015 15:22:00 -0000 Message-ID: Subject: Re: [RFC] Refactor autoconf options and build scripts To: Trevor Woerner Cc: "Jasmin J." , crossgcc Content-Type: text/plain; charset=UTF-8 X-IsSubscribed: yes X-SW-Source: 2015-09/txt/msg00045.txt.bz2 Well, here is the first serial build result: https://travis-ci.org/jmlemetayer/crosstool-ng/builds/80435130 Conclusion, doing serial build is space consuming ... :-) So we have to add some `rm` between each builds. I also tried to do parallel builds: https://travis-ci.org/jmlemetayer/crosstool-ng/builds/80447510 Travis CI handle this very well and as you can see it is easy to see which sample is good and which one is not. It is also more easy to read the log on failure. Personally, I think parallel builds could be a good option. Regards, JML 2015-09-15 16:39 GMT+02:00 Trevor Woerner : > On 09/15/15 10:21, Jean-Marie Lemetayer wrote: >> To continue the Jasmin work about Travis-CI, I have copy paste the >> Jasmin `.travis.yml` on my fork and add a script line to build all >> samples this way: >> >> for SAMPLE in $(./ct-ng list-samples 2>/dev/null | sed -n >> 's/^\[...\] *\(.*\)$/\1/p'); do ./ct-ng $SAMPLE; ./ct-ng build; done >> >> It seems to be working for now: https://travis-ci.org/jmlemetayer/crosstool-ng >> >> But going further into the Travis-CI documentation I see that the >> build timeouts after 50 minutes: >> http://docs.travis-ci.com/user/customizing-the-build/#Build-Timeouts >> >> So it seems not to be the good strategy as building all samples >> serially will take more than 50 minutes. But we could run parallel >> builds using matrix build: >> http://docs.travis-ci.com/user/customizing-the-build/#Build-Matrix >> >> The only difference is that we can't run build dynamically (using >> `list-samples`) and we have to say which samples we want to build for >> the continuous integration. > > Maybe you could rework your "for SAMPLE in..." script to run each sample > in a subprocess then wait for the results? > > http://stackoverflow.com/questions/356100/how-to-wait-in-bash-for-several-subprocesses-to-finish-and-return-exit-code-0 > > That way the number of sample is still generated dynamically, the > results can be collected to show if any fail (or if they all succeed), > and the whole build (hopefully) still takes less than 50 minutes? -- For unsubscribe information see http://sourceware.org/lists.html#faq