search

purebred-mua / purebred

A terminal based mail user agent based on notmuch
GNU Affero General Public License v3.0
139 stars 19 forks source link

The command "cabal new-build -w ${HC} ${TEST} ${BENCH} --project-file="cabal.project" --dep -j2 all" failed and exited with 1 during . #388

Closed romanofski closed 4 years ago

romanofski commented 4 years ago

Describe the bug All tests using cabal are currently failing and I can't spot exactly why. Log at the failure is:

$ cabal new-build -w ${HC} ${TEST} ${BENCH} --project-file="cabal.project" --dep -j2 all
Resolving dependencies...
Build profile: -w ghc-8.4.4 -O1
In order, the following will be built (use -v for more details):
 - base64-bytestring-1.1.0.0 (lib) (requires download & build)
 - purebred-email-0.4 (lib) (requires build)
Downloading  base64-bytestring-1.1.0.0
Downloaded   base64-bytestring-1.1.0.0
Starting     base64-bytestring-1.1.0.0 (lib)
Building     base64-bytestring-1.1.0.0 (lib)
Installing   base64-bytestring-1.1.0.0 (lib)
Completed    base64-bytestring-1.1.0.0 (lib)
Starting     purebred-email-0.4 (lib)
Building     purebred-email-0.4 (lib)
The command "cabal new-build -w ${HC} ${TEST} ${BENCH} --project-file="cabal.project" --dep -j2 all" failed and exited with 1 during .

Interestingly these dependencies weren't built in our previously passing tests, although now I wonder from where we always had installed purebred-email.

To Reproduce See current travis builds.

Expected behavior Passing tests

Screenshots See travis

Additional context None

frasertweedale commented 4 years ago

Ooh , I saw something (in an unrelated project) about a base64-bytestring change that is breaking stuff. Let me investigate.