9 Commits

Author	SHA1	Message	Date
Daniel Stenberg	5091e18e89	travis: run tests-nonflaky instead of tests-full	2017-03-22 10:55:10 +01:00
Sergei Nikulov	db3887632c	travis: removed option to rebuild autotool from source ... Fixes #943	2016-08-03 13:25:32 +02:00
Sergei Nikulov	120fe1a22d	travis: fix OSX build by re-installing libtool ... Apparently due to a broken homebrew install fixes #934 Closes #939	2016-08-01 15:08:53 +02:00
Jay Satiro	cb9ba5cf8d	Revert "travis: Install libtool for OS X builds" ... Didn't work. This reverts commit 50723585ed.	2016-07-28 00:52:44 -04:00
Jay Satiro	50723585ed	travis: Install libtool for OS X builds ... CI is failing due to missing libtoolize, so I'm trying this.	2016-07-28 00:36:55 -04:00
Jactry Zeng	1d89fd983a	travis.yml: Add OS X testbot.	2015-08-21 12:48:52 +02:00
Rémy Léone	b3c7f5159a	travis: Upgrading to container based build ... http://docs.travis-ci.com/user/migrating-from-legacy Closes #388	2015-08-20 23:28:05 +02:00
Jay Satiro	e424a1b3e7	.travis.yml: Change CI make test to make test-full ... - Change the continuous integration script to use 'make test-full' instead of just 'make test' so that the diagnostic log output is printed to stdout when a test fails. - Change the continuous integration script to use './configure --enable-debug' instead of just './configure' so that the memory analyzer will work during testing. Prior to this change Travis used its default C test script: ./configure && make && make test	2015-03-10 20:37:17 +01:00
Rémy Léone	be31924f8c	Adding a .travis.yml file to use the travis-ci.org ... From wikipedia: Travis CI is a hosted, distributed continuous integration service used to build and test projects hosted at GitHub. Travis CI is configured by adding a file named .travis.yml, which is a YAML format text file, to the root directory of the GitHub repository. Travis CI automatically detects when a commit has been made and pushed to a GitHub repository that is using Travis CI, and each time this happens, it will try to build the project and run tests. This includes commits to all branches, not just to the master branch. When that process has completed, it will notify a developer in the way it has been configured to do so — for example, by sending an email containing the test results (showing success or failure), or by posting a message on an IRC channel. It can be configured to run the tests on a range of different machines, with different software installed (such as older versions of a programming language, to test for compatibility).	2013-10-21 23:15:16 +02:00