Skip to content

Internal library tests in Cabal's package test suite fail on Windows #3147

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
grayjay opened this issue Feb 14, 2016 · 0 comments
Closed

Internal library tests in Cabal's package test suite fail on Windows #3147

grayjay opened this issue Feb 14, 2016 · 0 comments

Comments

@grayjay
Copy link
Collaborator

grayjay commented Feb 14, 2016

BuildDeps/InternalLibrary2:    FAIL (10.52s)
  executable should have linked with the internal library
  expected: "foofoomyLibFunc internal"
   but got: "foo\rfoo\rmyLibFunc internal"
BuildDeps/InternalLibrary3:    FAIL (7.24s)
  executable should have linked with the internal library
  expected: "foofoomyLibFunc internal"
   but got: "foo\rfoo\rmyLibFunc internal"
BuildDeps/InternalLibrary4:    FAIL (9.04s)
  executable should have linked with the installed library
  expected: "foofoomyLibFunc installed"
   but got: "foo\rfoo\rmyLibFunc installed"

Full log: https://ci.appveyor.com/project/grayjay/cabal/build/1.0.62

23Skidoo added a commit that referenced this issue Feb 14, 2016
Handle "\r\n" in internal library package tests (fixes #3147)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant