summaryrefslogtreecommitdiff
path: root/.gitlab-ci.yml
Commit message (Collapse)AuthorAgeFilesLines
* gitlab-ci: Fix URL of Darwin's cabal-install tarballBen Gamari2019-08-291-0/+1
| | | | | This was inadvertently referring to the cabal-install-latest/ directory which is volatile.
* gitlab-ci: Add Windows full build during the nightly pipelineBen Gamari2019-08-221-0/+13
|
* gitlab-ci: Update bootstrap compiled used for Darwin buildsBen Gamari2019-08-191-2/+2
|
* gitlab-ci: Manually set SPHINXBUILD on WindowsBen Gamari2019-08-041-0/+1
| | | | | | | For some reason configure seems unable to find it on its own. Let's try giving it a hint. Addresses #16398.
* gitlab-ci: Fix it after upgradeBen Gamari2019-07-311-2/+2
| | | | | It seems that the regular expression parser changed in GitLab 12.1 and now does now support forward slashes in the RE, even when escaped.
* gitlab-ci: Fix source tarball jobBen Gamari2019-07-241-3/+5
| | | | | | | | | | * Use show! in source tarball job. Since we aren't actually building anything in this job `show` won't work. * Fix Docker image name * Make `version` file contain only version string
* Hadrian: run the testsuite in Windows CI jobAlp Mestanogullari2019-07-231-2/+7
| | | | | | | | | | | | Since MR !1025 fixed the Windows build, allowing us to build a binary distribution, we can now run the testsuite in that CI job. This required fixing 'createFileLink': it should not try to create symlinks on Windows (that requires admin priviledges, which Hadrian can't assume). We now instead fall back to copying. This patch also removes some duplicated logic for iserv in the test rules, where we handle our dependency on the iserv binaries in a special way.
* Remove fix-submodules.pyÖmer Sinan Ağacan2019-07-231-7/+0
| | | | | Now that we have absolute paths for submodules (since a76b233d) we no longer need this script.
* gitlab-ci: Run slow validate in -debug jobBen Gamari2019-07-181-0/+2
| | | | | | | | Otherwise we don't compile the stage2 compiler with DEBUG, meaning the testsuite isn't checked with assertions. Metric Increase: haddock.Cabal
* gitlab-ci: Disable submodule linter for nowBen Gamari2019-07-151-1/+2
|
* gitlab-ci: Fix doc-tarball jobBen Gamari2019-07-031-0/+2
| | | | | | | Previously we used the deb9-debug job which used the `validate` build flavour which disabled `BUILD_SPHINX_PDF`. Fix this. Fixes #16890.
* gitlab-ci: Add testsuite typechecking lintBen Gamari2019-06-251-0/+13
|
* gitlab-ci: Run alpine builds during nightly jobBen Gamari2019-06-181-3/+12
|
* gitlab-ci: Run nofib on binary distributionswip/run-nofibBen Gamari2019-06-171-3/+44
| | | | Updates docker images to ensure that the `time` utility is available.
* gitlab-ci: Don't allow failure of deb9-dwarf jobBen Gamari2019-06-161-2/+1
| | | | This #16741 out of the way this should now pass.
* gitlab-ci: Build alpine release bindistsBen Gamari2019-06-161-0/+24
|
* gitlab-ci: Lint the lintersBen Gamari2019-06-141-0/+14
|
* gitlab-ci: Lint testsuite for framework failuresBen Gamari2019-06-141-0/+9
| | | | | This introduces a new lint job checking for framework failures and listing broken tests.
* gitlab-ci: Disable validate-x86_64-linux-deb9 job to reduce loadBen Gamari2019-06-131-2/+6
| | | | Enable artifacts on to ensure we have bindist coverage.
* gitlab-ci: Disable deb9-llvm job, introduce nightly LLVM jobBen Gamari2019-06-131-1/+12
| | | | | This should help alleviate queue times as the LLVM job is one of the longest that we have.
* Clean up .circleciBen Gamari2019-06-131-3/+3
| | | | Move prepare-system.sh to .gitlab and remove everything else.
* gitlab-ci: Don't build PDF user's guide on AArch64Ben Gamari2019-06-131-0/+2
| | | | | For reasons I don't understand sphinx seems to fail to produce a .idx file for makeindex.
* Hadrian: Do not allow the Linux jobs to fail anymoreAlp Mestanogullari2019-06-131-1/+0
| | | | | | MR !1151 makes the Hadrian/Linux job pass by fixing the last two test failures, so we can now be stricter and not allow those jobs to fail anymore, easily letting us see when patches introduce test failures.
* gitlab-ci: Bump Docker imageBen Gamari2019-06-121-1/+1
| | | | Fixes linters.
* gitlab-ci: Fetch submodules before running submodule linterBen Gamari2019-06-121-0/+2
|
* gitlab-ci: Test using slowtest in deb9-debug jobBen Gamari2019-06-121-0/+1
|
* gitlab-ci: Ensure that all commits on a branch are submodule-lintedBen Gamari2019-06-081-2/+2
| | | | | | | | | | The previous commit reworked things such that the submodule linter would only run on the head commit. However, the linter only checks the submodules which are touched by the commits it is asked to lint. Consequently it would be possible for a bad submodule to sneak through. Thankfully, we can use the handy CI_COMMIT_BEFORE_SHA attribute to find the base commit of the push.
* gitlab-ci: Fix submodule linting of commitsBen Gamari2019-06-081-8/+11
| | | | | There is no notion of a base commit when we aren't checking a merge request. Just check the HEAD commit.
* gitlab-ci: Disable shallow clonesBen Gamari2019-06-081-9/+5
| | | | | | | | | | | | | | | Previously we were passing `--unshallow` to `git fetch` in the linting rules to ensure that the base commit which we were linting with respect to was available. However, this breaks due to GitLab's re-use of working directories since `git fetch --unshallow` fails on a repository which is not currently shallow. Given that `git fetch --unshallow` circumvents the efficiencies provided by shallow clones anyways, let's just disable them entirely. There is no documented way to do disable shallow clones but on checking the GitLab implementation it seems that setting `GIT_DEPTH=0` should do the trick.
* gitlab-ci: A few clarifying commentsBen Gamari2019-06-081-0/+3
|
* gitlab-ci: Fix submodule linterBen Gamari2019-06-081-0/+6
| | | | | The job script didn't even try to compute the base commit to lint with respect to.
* gitlab-ci: Use --unshallow when fetching for lintersBen Gamari2019-06-081-2/+6
| | | | | | | GitLab creates a shallow clone. However, this means that we may not have the base commit of an MR when linting, causing `git merge-base` to fail. Fix this by passing `--unshallow` to `git fetch`, ensuring that we have the entire history.
* gitlab-ci: Don't run two submodule checking jobs on Marge jobsMatthew Pickering2019-06-081-0/+3
|
* gitlab-ci: Linters, don't allow to failMatthew Pickering2019-06-081-1/+0
| | | | | Ben disabled them in cd85f8a71bb56cff332560e1d571b3406789fb71 but didn't say how or why they were broken.
* gitlab-ci: Create index.html in documentation deploymentBen Gamari2019-06-071-0/+6
| | | | | Otherwise navigating to https://ghc.gitlab.haskell.org/ghc will result in a 404.
* Hadrian: use deb9 Docker images instead of deb8 for CI jobsAlp Mestanogullari2019-06-071-3/+3
| | | | | | | This should fix #16739, where we seem to be getting extra carets in a test's output because of the gcc that ships with the deb8 image, whule we're not observing those extra carets in the deb9-based (Make) jobs.
* gitlab-ci: Disable darwin hadrian jobMatthew Pickering2019-06-071-1/+2
| | | | | | | | See #16771 We don't have enough capacity for the two jobs currently. [skip ci]
* gitlab-ci: Run bindisttest during CIBen Gamari2019-06-041-0/+3
|
* Hadrian: fix OSX build failure and add an OSX/Hadrian CI jobAlp Mestanogullari2019-06-041-0/+40
| | | | | | | The OSX build failure introduced in 3aa71a22 was due to a change in the glob we use to collect libffi shared libraries in hadrian/src/Rules/Libffi.hs. This commit fixes the problem and adds an OSX CI job that builds GHC with Hadrian, to make sure we don't break it again.
* gitlab-ci: Use GHC 8.6.5 for Windows CI buildsBen Gamari2019-06-021-3/+3
|
* Add `-haddock` to prepare-system.sh and .gitlab-ci.ymlTakenobu Tani2019-06-021-0/+1
| | | | | | To cover ci conditions from ghc8.6 to 8.9, I add `-haddock` option to `.circleci/prepare-system.sh` and .gitlab-ci.yml. after including `mk/flavours/*`.
* Hadrian: always generate the libffi dynlibs manifest with globbingAlp Mestanogullari2019-05-301-1/+1
| | | | | | | | | | | | | | | Instead of trying to deduce which dynlibs are expected to be found (and then copied to the RTS's build dir) in libffi's build directory, with some OS specific logic, we now always just use `getDirectoryFilesIO` to look for those dynlibs and record their names in the manifest. The previous logic ended up causing problems on Windows, where we don't build dynlibs at all for now but the manifest file's logic didn't take that into account because it was only partially reproducing the criterions that determine whether or not we will be building shared libraries. This patch also re-enables the Hadrian/Windows CI job, which was failing to build GHC precisely because of libffi shared libraries and the aforementionned duplicated logic.
* Update .gitlab-ci.ymlBen Gamari2019-05-211-1/+1
|
* gitlab-ci: Allow Windows Hadrian build to failBen Gamari2019-05-211-1/+3
| | | Due to #16574.
* Restore the --coerce option in 'happy' configurationVladislav Zavialov2019-05-141-2/+2
| | | | | | happy-1.19.10 has been released with a fix for --coerce in the presence of higher rank types. This should result in about 10% performance improvement in the parser.
* gitlab-ci: Disable cleanup job on WindowsBen Gamari2019-05-101-27/+10
| | | | | | | As discussed in the Note, we now have a cron job to handle this and the cleanup job itself is quite fragile. [skip ci]
* Hadrian: generate JUnit testsuite report in Linux CI jobAlp Mestanogullari2019-05-031-2/+5
| | | | | | We also keep it as an artifact, like we do for non-Hadrian jobs, and list it as a junit report, so that the test results are reported in the GitLab UI for merge requests.
* Build Hadrian with -Werror in the 'ghc-in-ghci' CI jobAlp Mestanogullari2019-04-301-0/+1
|
* gitlab-ci: Reintroduce DWARF-enabled bindistsBen Gamari2019-04-251-0/+15
| | | | | It seems that this was inadvertently dropped in 1285d6b95fbae7858abbc4722bc2301d7fe40425.
* gitlab-ci: source-tarball job should have no dependenciesBen Gamari2019-04-241-0/+1
|
View Lorry Controller Status