summaryrefslogtreecommitdiff
path: root/.travis.yml
AgeCommit message (Collapse)Author
2016-05-11Fix a typo in travis config.Justin Latimer
2016-03-21testing: failing on arm is no longer an allowed failure!Paul Osborne
Signed-off-by: Paul Osborne <osbpau@gmail.com>
2016-03-17travis: add back testing on all rust versions (for linux)Paul Osborne
We are using containers for a majority of builds again, so perform those builds on more platforms (as travis seems to handle this much better). For OSX, we now testing i686/x86_64 on 1.1.0 as well for added coverage. Signed-off-by: Paul Osborne <osbpau@gmail.com>
2016-03-17travis: only require sudo on docker/i686 buildsPaul Osborne
Signed-off-by: Paul Osborne <osbpau@gmail.com>
2016-03-13testing: docker tests now work on travisPaul Osborne
All of the platforms tested currently fail in some way currently, but the infrastructure itself appears to be working. As we have moved to the legacy infrastructure (required in order to use docker), the tests do run slower now. To compensate for that, i686 builds are only done on stable and we do not test every version between the current stable and the oldest version we support. Signed-off-by: Paul Osborne <osbpau@gmail.com>
2016-03-13testing: first shot at testing with travis for arm, mips, android, ...Paul Osborne
This is based on libc and the new docker-based testing infrastructure via posborne/rust-cross. Signed-off-by: Paul Osborne <osbpau@gmail.com>
2016-03-05testing: increase stability by removing thread parallelismPaul Osborne
Currently, several of the tests are failing intermittently. After some research it appears that these failures only occur when thread parallelism is enabled (as is the case by default). To test, I just ran the failing tests over and over. I would consistently see errors when running the following: $ while true; do target/debug/test-7ec4d9681e812f6a; done When I forced single threaded execution, I no longer saw failures: $ while true; do RUST_TEST_THREADS=1 target/debug/test-7ec4d9681e812f6a; done I was mostly looking at the test_unistd failures which make calls out to fork() and then make subsequent calls to wait(). In that case there is one parent and the wait() called could (and frequently does) get some random child pid back because it just happened to terminate. That is why when one of the test fails so does the other one. I couldn't think of an obvious fix other than preventing thread parallelism in the short term. The tests still run very quickly. https://github.com/nix-rust/nix/issues/251 Signed-off-by: Paul Osborne <osbpau@gmail.com>
2016-01-29ci: Re-enable Travis builds for i686Kamal Marhubi
refs https://github.com/carllerche/nix-rust/issues/252
2016-01-28ci: Disable i686 buildsKamal Marhubi
They appear to be having intermittent build failures. Two builds at the same commit with different failures: - https://travis-ci.org/kamalmarhubi/nix-rust/builds/105335248 - https://travis-ci.org/kamalmarhubi/nix-rust/builds/105336327 refs https://github.com/carllerche/nix-rust/issues/252
2016-01-18ci: Test on Rust stable, beta, 1.1.0+Kamal Marhubi
refs https://github.com/carllerche/nix-rust/issues/238
2015-09-24Bump .travis.yml to Rust 1.1.0Geoffrey Thomas
2015-07-09Fix Travis doc buildsCarl Lerche
2015-07-09Run 32 bit CI buildsCarl Lerche
2015-07-08Run tests with one thread on travisCarl Lerche
2015-07-06Add feature flag around execvpeTilde Engineering
2015-05-28Deploy docs to S3Carl Lerche
2015-05-28Run CI on linux & os xCarl Lerche
2015-04-24Run CI on beta and nightlyCarl Lerche
2015-02-20Automatically deploy docsCarl Lerche
2015-01-03Added travis testsValerii Hiora