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

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

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

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

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

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

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

* This is only enabled with the lib flag.
* We tell users not to use the library in the package description.

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

This reverts commit bacdf19b.

'hackage-security' has been updated. I tested that build works now.

hackage-security hasn't been updated with new bounds, so this
unbreaks the build.

This reverts commit eec15a35.

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>

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>

Note: hackage-repo-tool doesn't build with Windows, so that
support is commented out.

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

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

See cabal-testsuite/README.md for a detailed description
of the new architecture.

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>

Now that we default to the secure repo, we need to run cabal update the
first time before running cabal (new-)build/etc, which is essentially
what the integration tests do. The travis and appveyor scripts already
did a cabal update at the beginning, but this one was using the
boostrap cabal and currently that version does not use the secure repo
format by default.

The key idea is that we define:

    type IO a = HasCallStack => Prelude.IO a

and voila, call stacks are maintained across all IO!  You can
look at the stacks using -v"debug +callstack".

There are a number of IO functions for which the call stack is
never used.  They are explicitly annotated using NoCallStackIO.
Maybe some day they will use call stacks and we can change their
types.  Similarly, there are a number of functions which do
have type IO, but then suppress the redundant constraint error
using "_ = callStack". Maybe some day we will attach call
stacks to the exceptions we throw.

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

This fixes #3687

Swithed AppVeyor test to GHC 8.0.1 because 7.10.3 is broken (https://chocolatey.org/packages/ghc/7.10.3) and added the `-y` option and `refreshenv` after installing GHC as suggested by Chocolatey

[ci skip]

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

See https://github.com/well-typed/hackage-security/pull/151.

This reverts commit 5a1f8575.

Cabal should be buildable out of the box.

The functions 'testWhen' and 'testUnless' filter tests in the 'TestTreeM' monad.
The option '--enable-all-tests' ignores filtering.  This commit also applies
filtering to the existing package tests that cannot run on Windows.

This reverts commit f211508d.