-
Notifications
You must be signed in to change notification settings - Fork 175
Test suite failure from Stackage build #611
Comments
Can you link me to or post the rest of the log output? Or alternatively how do I reproduce stackage's build environment? |
Sorry, that log file is no longer present. Reproducing the Stackage build environment is pretty tricky. Perhaps the relevant bit for those error message is that it passes in a --libexecdir flag. |
Why do you think it has to do with |
Maybe a bad guess based on the error message coming from readCreateProcess. |
cabal-helper-wrapper failing could have a number of reasons. If the executable wasn't there then the error code would be something like 127 (at least on linux IIRC) so I don't think it's that. All the other failure modes would print stuff on stderr which gets interleaved with the hspec output above the summary you copied out so I really do need the rest of the log to be able to say what's going on. |
Sorry, I can't provide that log right now. It's your call if you want to close this issue or leave it open. |
Can you catch it on the next stackage build or something? |
I'll try to, yes. It may take another few days, since Adam's on curator On Fri, Sep 18, 2015, 6:30 AM Daniel Gröber notifications@github.com
|
Ok great, thanks. |
Better late than never I tried it again, new errors now:
|
The only real error I can see is:
which I've never seen before. Isn't having colliding module names in a package-db a big no-no anyways? I guess Stackage shouldn't include packages that have colliding names or something? |
@DanielG I forgot to paste this link here: https://github.com/bergmark/blog/blob/master/2016/package-faq.md#ambiguous-modules-when-using-doctest and there's also the oldest open ticket on the stackage issue tracker :) commercialhaskell/stackage#416 |
The text was updated successfully, but these errors were encountered: