From: Ciro Santilli <ciro.santilli@gmail.com>
To: Simon Marchi <simon.marchi@polymtl.ca>
Cc: "gdb@sourceware.org" <gdb@sourceware.org>
Subject: Re: Travis CI setup
Date: Sun, 26 Jul 2015 11:51:00 -0000 [thread overview]
Message-ID: <CAFXrp_dCD93pXzWoG5Z9pdoREgdE6ivZwp68QUBrvgZ4g+oxvQ@mail.gmail.com> (raw)
In-Reply-To: <CAFXXi0nxiGzUd8Foyfw0M_8j1xCyd=_gD4sJ6rV7u-Hz9tWCjw@mail.gmail.com>
Thanks for the tip! I have added it as well, and the number of tests did go up.
I think on 14.04 apt-get build-dep installs it, but apparently not in 12.04.
On Sat, Jul 25, 2015 at 7:42 PM, Simon Marchi <simon.marchi@polymtl.ca> wrote:
> On 25 July 2015 at 13:34, Ciro Santilli <ciro.santilli@gmail.com> wrote:
>> I've made a Travis CI build at:
>> https://github.com/cirosantilli/binutils-gdb/tree/gdb/travis
>>
>> It runs in an Ubuntu 12.04 AMD64 machine.
>>
>> It finishes in 20 minutes with 30 errors:
>> https://s3.amazonaws.com/archive.travis-ci.org/jobs/72605568/log.txt ,
>> less than the 46 on my Ubuntu 14.04 machine, and the same Buildbot
>> commit result.
>>
>> With parallel tests make -j$(ncpus) it runs in 4 minutes, but the
>> error rate goes up.
>>
>> Best of all: free testing infrastructure, that can be used by anyone
>> to test commits on branches before they are merged.
>>
>> Let me know if the build steps on the .travis.yml can be improved
>> somehow to reduce false errors.
>
> Hi Ciro,
>
> You could install the systemtap-sdt-dev package, that would allow
> running the tests that currently exit early with:
>
> fatal error: sys/sdt.h: No such file or directory
>
> They probably show as untested or unsupported right now, so it won't
> reduce the number of failures, just raise the number of passes.
>
> Simon
prev parent reply other threads:[~2015-07-26 11:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-25 17:34 Ciro Santilli
2015-07-25 17:42 ` Simon Marchi
2015-07-26 11:51 ` Ciro Santilli [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAFXrp_dCD93pXzWoG5Z9pdoREgdE6ivZwp68QUBrvgZ4g+oxvQ@mail.gmail.com \
--to=ciro.santilli@gmail.com \
--cc=gdb@sourceware.org \
--cc=simon.marchi@polymtl.ca \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox