Josh Kalderimis authored 6 years ago and Edward Z. Yang committed 6 years ago

* use sudo: true on travis ci

* minor comment to explain previous change

This relies on having 4 core 16 gigs Travis machines enabled for the account.

7.4 is out of our support window, so it's not really important to consider for the status of a PR (and can contribute to error fatigue)

This ought to fix the build matrix. I believe the issue is GHC trac
5129, where evaluate is being miscompiled: in cabal-testsuite's
Test.Cabal.Server, in the function readUntilEnd, the 'read' function
is protected by an 'if' to ensure that it doesn't result in the
dreaded 'no parse'. However, some sophisticated putStrLn
debugging has revealed that it is being called in *both* branches, not
just the safe one; this is the worst sort of heisenbug because it
vanished when I put a putStrLn before the evaluate!

Since the evaluate function is fixed in 8.4.2 and bumping to 8.4.2
has a patch for trac 5129, this is as fixed as it can get.

This reverts commit 0e3718c4.

tracetree was updated for GHC 8.4.1 in version 0.1.0.2.

The flag debug-tracetree requires tracetree, which hasn't yet been updated for
GHC 8.4.1.

[ci skip]

GHC 7.8.4 was released in Dec 2014, so this is in accordance with our
support policy. NB: doesn't affect lib:Cabal.

Fixes #4856.

- Manually generate Lexer.hs
- Temporarily disable parser-hackage-tests on appveyor (needs
  01-index.tar)
- Add root Makefile to handle commmon dev tasks (genering Lexer.hs)

This benchmark is based off of a script written by @kosmikus.  It adds
functionality for running multiple trials for each package, but it is currently
missing other features.

- cabal-install 2.0 new-build has different directory
  layout; everything is adjusted for that.
- Using hvr's PPA for Linux builds, and a custom
  ezyang build for OS X

Herbert Valerio Riedel authored 7 years ago and Mikhail Glushenkov committed 7 years ago

GHC 8.2.1 appears to take significantly longer to compile the code
and pushes us over the Travis job time limit.

Signed-off-by: Edward Z. Yang <ezyang@cs.stanford.edu>

Signed-off-by: Edward Z. Yang <ezyang@cs.stanford.edu>

Edward Z. Yang authored 8 years ago and Edward Z. Yang committed 8 years ago

- Setup the ssh key for cabal-website deploy right before we use
  it, so it doesn't get clobbered by our pushbot deploy script.
  Furthermore, umask the key to 600, so that we can override it.

- Add some more helpful information to the Pushbot commit messages,
  including what branch/PR the build was for, and a link to the
  relevant GitHub page.

- Have Travis spoof the author and email of the original committer,
  so that Travis sends the build notification message to the right place.

Signed-off-by: Edward Z. Yang <ezyang@cs.stanford.edu>

Edward Z. Yang authored 8 years ago and Edward Z. Yang committed 8 years ago

Signed-off-by: Edward Z. Yang <ezyang@cs.stanford.edu>

Edward Z. Yang authored 8 years ago and Edward Z. Yang committed 8 years ago

Signed-off-by: Edward Z. Yang <ezyang@cs.stanford.edu>