From: Cyril Hrubis <chrubis@suse.cz>
To: ltp@lists.linux.it
Subject: [LTP] [PATCH v2 1/2] travis: use various gcc and clang versions + using containers
Date: Mon, 16 Jan 2017 11:25:19 +0100 [thread overview]
Message-ID: <20170116102519.GC20956@rei.lan> (raw)
In-Reply-To: <20170113090706.29130-1-pvorel@suse.cz>
Hi!
> Using containers is declared to be faster, but does not allow us to use
> sudo => install into $HOME.
>
> Signed-off-by: Petr Vorel <pvorel@suse.cz>
Applied thanks.
> ---
> Used gcc: 4.6, 4.7, 4.8. 4.9, 5, 6
> Used clang: 3.5, 3.8, 3.9
>
> I simplified patch. This way we cannot install clang-3.3, but I suppose it's ok.
> Which versions are you interested? We can have even more versions, but even this subset is IMHO quite a lot.
I guess that we cover more than enough compiler versions now.
What I would be intersted in in the long term would be running LTP build
on some sligthly older distribution (debian stable or oldstable should
be quite easy with debootstrap) as well as do a 32bit build [1]. So
maybe we can omit build for some gcc versions and rather work on these
two options.
[1]
https://github.com/patricksnape/test-travis-chroot-32/blob/master/setup_travis.sh
--
Cyril Hrubis
chrubis@suse.cz
next prev parent reply other threads:[~2017-01-16 10:25 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-13 9:07 [LTP] [PATCH v2 1/2] travis: use various gcc and clang versions + using containers Petr Vorel
2017-01-13 9:07 ` [LTP] [PATCH v2 2/2] make: print compiler version Petr Vorel
2017-01-16 10:27 ` Cyril Hrubis
2017-01-16 10:25 ` Cyril Hrubis [this message]
2017-01-16 13:54 ` [LTP] [PATCH v2 1/2] travis: use various gcc and clang versions + using containers Petr Vorel
2017-01-16 14:04 ` Cyril Hrubis
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=20170116102519.GC20956@rei.lan \
--to=chrubis@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