1
1
Граф коммитов

13 Коммитов

Автор SHA1 Сообщение Дата
Gilles Gouaillardet
d37f35244f travis: fix make distcheck
bad side effect occurs when CPPFLAGS is set in the environment,
so set it (and LDFLAGS too) on the configure command line.

Signed-off-by: Gilles Gouaillardet <gilles@rist.or.jp>
2019-10-09 12:57:54 +09:00
Howard Pritchard
f06a5d93ea travis: remove os-x from OS test matrix
Signed-off-by: Howard Pritchard <howardp@lanl.gov>
2017-03-21 10:36:30 -06:00
Gilles Gouaillardet
ab5e86c97d travis: install hwloc packages
Signed-off-by: Gilles Gouaillardet <gilles@rist.or.jp>
2017-02-27 14:40:35 +09:00
Gilles Gouaillardet
ebb43c59d9 travis: cope with brew upgrade failure
also try to brew install gcc before brew upgrade gcc
2016-10-05 09:50:34 +09:00
Gilles Gouaillardet
af7fd57b45 travis: always run 'brew update; brew upgrade automake libtool' on OSX 2016-09-21 13:41:44 +09:00
Gilles Gouaillardet
af23dcc123 travis: use gcc 6 and run brew upgrade
brew update seems to remove /usr/local/Library/ENV, which breaks glibtool,
so manually upgrade a few formulas
2016-07-20 15:48:36 +09:00
Gilles Gouaillardet
46710ba151 travis: fix a typo and create bogus directories to avoid compiler warnings 2016-05-26 15:28:10 +09:00
Jeff Squyres
bd04192087 Merge pull request #1234 from ggouaillardet/poc/travis_gcc5
Poc/travis gcc5
2016-01-18 09:26:56 -05:00
Jeff Squyres
f8722a96a6 travis: add a bunch of comments explaining things 2016-01-05 10:54:39 -08:00
Gilles Gouaillardet
143ea18ffa test gcc5 in travis 2015-12-18 09:16:25 +09:00
Jeff Squyres
d668612f16 travis: update comment
Update the comment explaining why we don't build the verbs libfabric
provider (because Open MPI doesn't use it).  Specifically: the
upstream libfabric bug about building libfabric under travis has been
fixed -- so that's no longer the reason we don't build it.
2015-12-16 05:45:16 -08:00
Jeff Squyres
a4a17c2836 travis: use "make -k" to see all failures
One of the criticisms of Travis on the call earlier today was that
when there's a compile failure, you really only see the *first*
compile failure.  Then you fix that, resubmit, and 15-60 minutes
later, you see the *next* compile failure.

Per some discussion with @bosilca and @rhc54 this afternoon, use "make
-k", which will have "make" try to continue the build even after
compile failures.  Hence, you'll be able to see many more compile
errors that just one at a time.

In some cases (e.g., if there's a typo in a top-level header file), it
will cause a bazillion lines of compile error output, but hopefully
that should be easy to spot / ignore.
2015-12-15 17:07:01 -05:00
Jeff Squyres
357ca4ffd2 travis: add config file for travis-ci.org 2015-12-14 13:05:59 -08:00