| Commit message (Collapse) | Author | Age |
|---|
| |
|
|
|
|
|
|
| |
https://docs.travis-ci.com/user/trusty-ci-environment
all trusty images have sudo, and actually it is required
to use this new Travis environment per docs. This makes
it actually do it. Clang is 3.5 now.
|
| |
|
|
|
|
|
|
|
| |
Upgraded to using Tavis trusty dist (from precise)
Ubuntu's clang is only 3.4 though.
For fancy address, thread-sanitizer stuff, easier to do on OS X.
We can use the clang that comes with xcode 8 beta.
|
| |
|
|
|
|
|
| |
Clang repositories currently offline, causing build errors.
Can be reverted once https://github.com/travis-ci/travis-ci/issues/6120
is fixed.
|
| | |
|
| |
|
|
|
|
|
|
| |
Since #2849 was merged, there are no further leaks detected by the
address sanitiser. This makes it a good target to enable for Travis,
which will enable regression testing.
Closes #2851.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
I noticed while fixing issue #2702 that the fish program being tested
was sourcing config.fish files outside of the current build. This also
happens when Travis CI runs the tests but isn't an issue there because
of how Travis is configured to execute the tests.
I also noticed that running `make test` was polluting my personal fish
history; which will become a bigger problem if and when the fishd universal
var file is moved from $XDG_CONFIG_HOME to $XDG_DATA_HOME.
This change makes it possible for an individual to run the tests on
their local machine secure in the knowledge that only the config.fish and
related files from their git repository will be used and doing so won't
pollute their personal fish history.
Resolves #469
|
| |
|
|
|
|
| |
The values for notification hooks remain available as comments, but this
prevents notifications from other repositories from automatically being
linked across to the official notification channels.
|
| |
|
|
|
| |
Leak checking is disabled for now as it has the potential to produce too
many false positives.
|
| |
|
|
|
| |
From
http://docs.travis-ci.com/user/migrating-from-legacy/
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
| |
As far as I know we can't access the build artifacts from Travis, so we
can't check the interactive logs after a test failure. Add an
environment variable that causes the test runner to dump the logs
itself, and set that variable for Travis.
|
| |
|
|
|
|
|
| |
This was apparently what was interfering with the tests working on
Linux.
Tweak .travis.yml to install expect so the tests run on Linux.
|
| | |
|
| | |
|
| |
|
Aaron Gyes
David Adam
Kurtis Rader
Bruno Pinto
Kevin Ballard
Konrad Borowski