Skip to content
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

Errors in hie unit test suite involving cabal-helper since 04c2d34 #98

Closed
jneira opened this issue Feb 11, 2020 · 3 comments
Closed

Errors in hie unit test suite involving cabal-helper since 04c2d34 #98

jneira opened this issue Feb 11, 2020 · 3 comments

Comments

@jneira
Copy link
Collaborator

jneira commented Feb 11, 2020

1) CabalHelper, cabal-helper spec, cradle discovery and loading, dummy filepath, finds none-cradle, stack repo
       uncaught exception: IOException of type NoSuchThing
       D:\ws\haskell\haskell-ide-engine\test\testdata\cabal-helper\simple-stack\.stack-work\dist\e626a42b\setup-config: openFile:
does not exist (No such file or directory)
  • I've checked that effectively the D:\ws\haskell\haskell-ide-engine\test\testdata\cabal-helper\simple-stack\.stack-work\dist dir does not exist
  • Then i've started to bisect cabal-helper commits since the hackage released version and i've found that the commit that triggers the error is 04c2d34 (1c0f2e8 works fine but it does not create the dist folders)

(NOTE: it would be great to have hackage releases/revisions tagged in github, to help diagnose those kind of bugs)

@jneira
Copy link
Collaborator Author

jneira commented Feb 11, 2020

For completeness git revert 04c2d34 makes the tests pass so the last commits after it look good

@DanielG
Copy link
Owner

DanielG commented Feb 11, 2020

Thanks for bisecting that, I must have pushed that commit by accident before finishing testing. Not sure how that happened..

@DanielG
Copy link
Owner

DanielG commented May 2, 2020

This was fixed by a18bbb2, and the commit is now part of #108.

@DanielG DanielG closed this as completed May 2, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants