From: Petr Vorel <pvorel@suse.cz>
To: ltp@lists.linux.it
Subject: [LTP] [RFC PATCH 0/4] Travis enhancements
Date: Wed, 29 Nov 2017 20:07:58 +0100 [thread overview]
Message-ID: <20171129190758.GC3573@x230> (raw)
In-Reply-To: <20171129154413.GC15160@rei>
Hi Cyril,
> > I've added several travis enhancements, most notably added 32bit cross-compile
> > build and added more compilers (add gcc-7, clang-4.0, clang-5.0, remove clang-3.9).
> > Now there is 12 builds instead of 9, speed increased from ~13 min [1] to ~26 min [2],
> > which is maybe to much. If we don't like it, we can decide which compilers to have.
> Well we can cut a few compiler versions, perhaps just keep the latest
> for each major number, that should catch most of the problems I guess.
Thanks for an input! OK, I'll drop gcc 4.6, 4.7, 4.8 and clang 3.5, 3.8.
So we'll have gcc 4.9, 5.x, 6.x, 7.x and clang 3.9, 4.0 and 5.0
Unfortunately I haven't manage to add gcc 8.
Kind regards,
Petr
prev parent reply other threads:[~2017-11-29 19:07 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-28 23:21 [LTP] [RFC PATCH 0/4] Travis enhancements Petr Vorel
2017-11-28 23:21 ` [LTP] [RFC PATCH 1/4] travis: Add build script Petr Vorel
2017-11-29 8:13 ` Li Wang
2017-11-29 8:27 ` Petr Vorel
2017-11-29 8:41 ` Li Wang
2017-11-29 14:52 ` Petr Vorel
2017-11-29 15:42 ` Cyril Hrubis
2017-11-29 18:31 ` Petr Vorel
2017-11-30 2:09 ` Li Wang
2017-11-28 23:21 ` [LTP] [RFC PATCH 2/4] travis: Add 32 cross-compile build + use build.sh Petr Vorel
2017-11-29 15:45 ` Cyril Hrubis
2017-11-28 23:21 ` [LTP] [RFC PATCH 3/4] travis: Add gcc-7, clang-4.0, clang-5.0, remove clang-3.9 Petr Vorel
2017-11-28 23:21 ` [LTP] [RFC PATCH 4/4] travis: Install all dependencies (headers and libraries) Petr Vorel
2017-11-29 15:48 ` Cyril Hrubis
2017-11-29 18:59 ` Petr Vorel
2017-11-29 15:44 ` [LTP] [RFC PATCH 0/4] Travis enhancements Cyril Hrubis
2017-11-29 19:07 ` Petr Vorel [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=20171129190758.GC3573@x230 \
--to=pvorel@suse.cz \
--cc=ltp@lists.linux.it \
/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