summaryrefslogtreecommitdiff
path: root/.travis.yml
Commit message (Collapse)AuthorAgeFilesLines
* Attempt to fix travis buildMichael Sloan2018-07-121-3/+3
|
* Revert installing texinfo in CI systemsJoachim Breitner2017-10-031-1/+0
| | | | | This reverts commit 00ff02352f07bff7d422e4e48e4e5df9a0b63d83. This reverts commit 11a59de25d49f999eed0ea55df29d916a66ecd91.
* Travis: Install texinfoJoachim Breitner2017-10-021-0/+1
|
* Travis: Boot with ghc-8.2.1, and disable test suiteJoachim Breitner2017-09-071-6/+7
| | | | | | by only building, we can hopefully be in the build time limit, while still providing a bit of useful service, e.g. indicating early when GitHub pull requests (with seemingly innocent results) fail to build.
* Travis: Add dependency on python3Ben Gamari2016-12-011-0/+1
| | | | The testsuite now requires python >=3.0. See #12909.
* Travis: llvm's apt repository is offlineThomas Miedema2016-06-021-2/+4
|
* travis: use GHC 7.10.3Herbert Valerio Riedel2015-12-311-2/+2
|
* travis: use LLVM 3.7Austin Seipp2015-10-131-3/+3
| | | | Signed-off-by: Austin Seipp <austin@well-typed.com>
* Move user's guide to ReStructuredTextBen Gamari2015-10-031-3/+2
|
* Testsuite: by default run all tests for a single wayThomas Miedema2015-09-021-0/+2
| | | | | | | | | | | | | | `make test` now runs all tests for a single way only. Use `make slowtest` to get the previous behaviour (i.e. run all tests for all ways). The intention is to use this new `make test` setting for Phabricator, as a reasonable compromise between `make fasttest` (what it previously used) and a fullblown `make slowtest` (which runs all tests for all ways). See Note [validate and testsuite speed] in toplevel Makefile. Differential Revision: https://phabricator.haskell.org/D1178
* Travis: prevent 10' no output, by setting VERBOSE=2Thomas Miedema2015-08-171-1/+6
|
* Travis: do pass `--quiet` to validateThomas Miedema2015-07-221-3/+1
| | | | | | | | It's failing at the moment with "The log length has exceeded the limit of 4 Megabytes". We don't seem to have periods of >10 minutes without output after all, which was the initial reason of not using `--quiet`.
* Validate: explain THREADS instead of CPUS in --helpThomas Miedema2015-07-221-1/+1
|
* Travis: use ghc-7.8.4 as stage0 to fix the buildThomas Miedema2015-07-211-2/+2
|
* Travis: actually do debug buildsThomas Miedema2015-07-181-1/+1
|
* traivs: Use the new container based travis setupJoachim Breitner2015-07-141-11/+16
| | | | | which supposedly has more resources, so maybe this makes travis useful for us again.
* Travis: use apt-get -qThomas Miedema2015-06-111-3/+3
| | | | [skip ci]
* Travis: allow user forksThomas Miedema2015-06-041-6/+15
| | | | | | | | | | | | Check for each submodule repository url if the user made its own fork. If so, use that. Otherwise, fall back on the one from github.com/ghc. As suggested by Richard in this mailinglist discussion: https://mail.haskell.org/pipermail/ghc-devs/2014-November/007300.html Documentation is at [wiki:TestingPatches#Travis]. Differential Revision: https://phabricator.haskell.org/D939
* Make validate more quietThomas Miedema2015-06-041-2/+3
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | * By default use V=0, and call the testsuite with VERBOSE=2, which we did before only with validate --quiet. This disables printing the test commands it runs. * When --quiet is used, call the testsuite with VERBOSE=1. This disables printing the '====> Scanning' lines, and doesn't print which test is being run. So it only prints something when a test accidentally prints to stdout or when it fails. Don't set this option on Travis, as Travis will cancel a build if it doesn't see any output for more than 10 minutes. * When --quiet is used, set the new test option NO_PRINT_SUMMARY, which skips printing the test summary. Only the list of unexpected failures is printed, if there are any. Note that the full summary can still be found in testsuite_summary.txt * When --quiet is used, don't pass the `-v` flag to `ghc-pkg check` * When --quiet is used, don't print the Oops! header. It shoud be clear from the list of failing tests that something is wrong. This is all done to get the most out of 30 lines of logfile. These changes can be disabled later by simply not passing the --quiet flag to validate. Differential Revision: https://phabricator.haskell.org/D942
* Travis: Send notifications to author and commiterJoachim Breitner2015-06-041-5/+0
| | | | | | | This is the Travis default. It should only spam people who have an GitHub account and are a member of the ghc organization on GitHub, as noted by thomie on https://phabricator.haskell.org/D939#25497. Let's see how that works out.
* Travis: use validate --quiet to prevent hitting log file limitsThomas Miedema2015-05-311-2/+2
| | | | | | | Currently, this will use `make -s` instead of `make`, such that `make` doesn't echo the commands it's going to run. And second, it calls the testdriver with a lower verbosity, such that the shell commands it runs don't get printed either.
* travis: Get libstdc++ from a more sensible locationJoachim Breitner2015-03-041-2/+2
|
* Unbreak travis by installing llvm-3.6Joachim Breitner2015-02-211-3/+5
|
* Use llvm-3.5 on TravisJoachim Breitner2014-12-161-2/+4
| | | | | to avoid a build failure with T5681(optllvm). According to Ben Gamari, llvm-3.4 is known to be not working with GHC HEAD.
* travis: Use hvr’s multi-ghc-PPAJoachim Breitner2014-08-191-5/+8
|
* Unbreak travis by not passing --no-dphJoachim Breitner2014-08-111-1/+1
|
* Revert "travis: Install process via cabal"Joachim Breitner2014-07-211-2/+2
| | | | | | | This reverts commit c41b716d82b1722f909979d02a76e21e9b68886c. With the Cabal bump reverted, this should build again, and we aim to keep it buildable like this.
* travis: Install process via cabalJoachim Breitner2014-07-191-2/+2
| | | | | and install to global data base (bad practice, but ok on a throw-away CI system).
* Build on travis with CPUS=2Joachim Breitner2014-07-171-1/+1
| | | | | | With CPU=3 we are hitting resoure limits (probably memory). With CPU=2 this is less likely to happen. We will get more random timeouts, but these are more easily spotted, and marked as "Failure", not as "Error".
* Add a .travis.yml fileJoachim Breitner2014-07-121-0/+36
This is a reduced build that should finish within the 50 minute time limit most of the time. In particular, * it skips DPH * it does not build dynamic libraries and no dynamic executables * does not build haddock or generate documentation * only runs fast tests, and no performance tests You can see its results at https://travis-ci.org/ghc/ghc/builds
View Lorry Controller Status