| Age | Commit message (Collapse) | Author |
|---|
|
|
|
Fixes #943
|
|
Apparently due to a broken homebrew install
fixes #934
Closes #939
|
|
Didn't work.
This reverts commit 50723585ed380744358de054e2a55dccee65dfd7.
|
|
CI is failing due to missing libtoolize, so I'm trying this.
|
|
|
|
http://docs.travis-ci.com/user/migrating-from-legacy
Closes #388
|
|
- 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
|
|
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).
|
