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.

Sign up for GitHub

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

Jump to bottom

appveyor builds have been failing again #832

Closed
simonmichael opened this issue Jul 2, 2018 · 4 comments
Closed

appveyor builds have been failing again #832

simonmichael opened this issue Jul 2, 2018 · 4 comments
Labels
A-BUG Something wrong, confusing or sub-standard in the software, docs, or user experience. platform:windows tools hledger developer tools, scripts, processes..

Comments

@simonmichael
Copy link
Owner

simonmichael commented Jul 2, 2018 •
edited
Loading

Due to (still) not being able to find the happy executable, apparently.
https://ci.appveyor.com/project/simonmichael/hledger/history

Possibly related:
commercialhaskell/stack#595
commercialhaskell/stack#3178
commercialhaskell/stack#3249
https://www.fpcomplete.com/blog/2017/07/stacks-new-extensible-snapshots
@simonmichael simonmichael added A-BUG Something wrong, confusing or sub-standard in the software, docs, or user experience. platform:windows tools hledger developer tools, scripts, processes.. labels Jul 2, 2018
@simonmichael simonmichael mentioned this issue Jul 2, 2018
Closed
@simonmichael
Copy link
Owner Author

simonmichael commented Jul 2, 2018 •
edited
Loading

Reported as commercialhaskell/stack#4125.

@simonmichael
Copy link
Owner Author

simonmichael commented Jul 11, 2018 •
edited
Loading

Fixed for now by using unreleased stack. To avoid rebuilding that every time, we save the stack executable in appveyor cache. This will break when cache is cleared, and possibly also when appveyor picks a different instance with different cache state. After next stack release, we can resume downloading the binary again and close this.

@simonmichael
Copy link
Owner Author

Same workaround now applied on 1.10 branch, to generate windows 1.10 binaries.

simonmichael added a commit that referenced this issue Jul 11, 2018
@simonmichael
site: download: update appveyor links (#832)
acff169 
[ci skip]
simonmichael added a commit that referenced this issue Jul 17, 2018
@simonmichael
tools: appveyor: show bin dir, indicating cache status (#832)
49b3751 
[ci skip]
simonmichael added a commit that referenced this issue Jul 17, 2018
@simonmichael
site: download: mention #832 again
56704af 
[ci skip]
simonmichael added a commit that referenced this issue Oct 24, 2018
@simonmichael
appveyor: use easytest 0.2.1 avoiding unicode output (may help #832)
8f50e82
@simonmichael
Copy link
Owner Author

Building with stack 1.9, ghc 8.6, seems in good shape now.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
A-BUG Something wrong, confusing or sub-standard in the software, docs, or user experience. platform:windows tools hledger developer tools, scripts, processes..
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@simonmichael