stack 1.7.1 still has problems finding build tools ("The program 'happy' is required") #4125

simonmichael · 2018-07-02T08:23:44Z

General summary/comments (optional)

hledger appveyor builds are failing due to not being able to find "happy" when building pretty-show, haskell-src-exts, language-javascript. simonmichael/hledger#832

I saw this a month ago and tried several things to fix it, and probably thought I had solved it by upgrading to stack 1.7.1, but now it seems not.

Possibly related:
#595
#3178
#3249

Steps to reproduce

I don't have a short repro, instead I'll point to appveyor logs.

Expected

Successful builds of pretty-show, haskell-src-exts, language-javascript.

Actual

These packages failed to build due to "missing happy", even with stack 1.7.1. Eg see
https://ci.appveyor.com/project/simonmichael/hledger/build/master-460.

Some more details:

hledger build history: https://ci.appveyor.com/project/simonmichael/hledger/history.
Only the full, >30m builds are building pretty-show etc.

The last full build that succeeded was https://ci.appveyor.com/project/simonmichael/hledger/build/master-451 on 26 May. The stack version is not reported, but it fetched http://www.stackage.org/stack/windows-x86_64, and stack 1.7.1 was released on 27 Apr, so I would have thought it was using stack 1.7.1. Unless there was some path issue.

The next full build, 456 on 30 May, failed with No packages found in snapshot which provide a "happy" executable, which is a build-tool dependency of "pretty-show" warnings and The program 'happy' version >=1.19 is required but it could not be found errors. So did build 460 and later, and these report the stack version as definitely 1.7.1. https://ci.appveyor.com/project/simonmichael/hledger/build/master-460.

Builds 459, 462 and 465 were non-full builds that succeeded by luck, appveyor apparently picks randomly from several build instances each with their own cache state.

Stack version

1.7.1

Method of installation

Official binary, downloaded from stackage.org or fpcomplete's package repository

The text was updated successfully, but these errors were encountered:

mihaimaruseac · 2018-07-02T13:23:21Z

Can you also try with the stack from HEAD? stack upgrade --git and then build again.

I think this has been solved on master, accidentally, but I'm not completely sure.

simonmichael · 2018-07-02T15:13:33Z

I'll report back.. it's taking a while.

simonmichael · 2018-07-02T17:16:26Z

I can still reproduce with stack-git: https://ci.appveyor.com/project/simonmichael/hledger/build/master-497

snoyberg · 2018-07-04T12:22:37Z

As part of #3922, I was discussing the behavior of the build tool detection with @bitemyapp. It might make sense to copy the behavior that cabal-install 2.0 (or 2.2?) added for build tool detection, which unless I'm mistaken comes down to something like:

For new cabal files, build tools must be specified including the package they come from
For old cabal files, there's a hard-coded mapping from build tool name to the package it comes from

That would likely bypass many cases where it becomes difficult/impossible to determine which package was intended, as well as allow us to much more lazily parse cabal files (since we needn't know all executables provided by all packages in a snapshot).

snoyberg · 2018-07-04T14:21:06Z

BTW, adding an explicit stack build happy to your CI scripts should be a decent workaround in the short term unless I'm mistaken @simonmichael.

snoyberg · 2018-07-04T14:26:26Z

Sorry, last comment for a bit: do you have any kind of local repro for this? I haven't been able to trigger it on my OS X system at least.

simonmichael · 2018-07-04T14:38:18Z

I don't, sorry. I don't see it on mac either, or gnu/linux.

https://ci.appveyor.com/project/simonmichael/hledger/build/master-458?fullLog=true seems to show that explicitly pre-installing happy didn't help (again unless I'm missing some path issue like a .\happy.exe, but I don't think so).

snoyberg · 2018-07-04T17:32:57Z

@simonmichael could you try using the 4125-cabal-style-build-tools branch of Stack and see if that fixes things for you? We'd still need to make sure this is the right solution before merging to master, but having data that it solves this bug would be great.

simonmichael · 2018-07-04T21:08:18Z

@snoyberg sorry but I've had trouble installing this branch of stack. I've been trying upgrade --git-branch, but this fails ("you are already running the most recent version") with stack-1.7.1 or with a recent stack-81889990.
https://ci.appveyor.com/project/simonmichael/hledger/build/master-503#L15
https://ci.appveyor.com/project/simonmichael/hledger/build/master-505?fullLog=true#L34

mihaimaruseac · 2018-07-04T22:45:37Z

What I'd do would be to clone the repo and checkout the branch then stack build and stack exec stack -- <arguments>. I think this should work

snoyberg · 2018-07-05T04:35:26Z

I think that's because you're missing the --git flag, but I'm not sure. I'm forked the repo and I'm trying to kick off a build myself: https://ci.appveyor.com/project/snoyberg/hledger

simonmichael · 2018-07-05T05:31:20Z

Doh, you're right. ~~https://ci.appveyor.com/project/simonmichael/hledger/build/master-511 might show what we want.~~

snoyberg · 2018-07-05T08:00:15Z

It looks to me like my AppVeyor build didn't have this bug. The build failed, but that seems to be for an unrelated reason (maybe a timeout?). Can you confirm @simonmichael?

simonmichael · 2018-07-05T08:14:24Z

Your latest looks good! And mine too.
https://ci.appveyor.com/project/snoyberg/hledger/build/1.0.3?fullLog=true
https://ci.appveyor.com/project/simonmichael/hledger/build/master-512?fullLog=true

mihaimaruseac · 2018-07-05T13:26:32Z

So I gather that #4132 solves this, 👍

…d-tools Use a hard-coded tool dependency map (fixes #4125)

Note that the previous workaround for #4125 should no longer be necessary because: 1. Stack 1.9 will not suffer from that bug 2. To my knowledge, custom snapshots never suffered from that bug Guess we'll find out when Travis takes a crack at this though!

This bumps us to newer versions of some libraries, in particular conduit, which were previously blocked by #4125. Using a custom snapshot should allow this by bypassing that bug.

simonmichael mentioned this issue Jul 2, 2018

appveyor builds have been failing again simonmichael/hledger#832

Closed

mihaimaruseac added type: bug needs reproduction further investigation required component: build component: extensible-snapshots awaiting-response labels Jul 2, 2018

mihaimaruseac removed awaiting-response needs reproduction labels Jul 2, 2018

snoyberg added a commit that referenced this issue Jul 4, 2018

Use a hard-coded tool dependency map (fixes #4125)

3017b65

snoyberg mentioned this issue Jul 4, 2018

Use a hard-coded tool dependency map (fixes #4125) #4132

Merged

2 tasks

snoyberg added the need confirmation label Jul 4, 2018

snoyberg added a commit that referenced this issue Jul 4, 2018

Use a hard-coded tool dependency map (fixes #4125)

0bf5e1d

snoyberg added a commit that referenced this issue Jul 4, 2018

Use a hard-coded tool dependency map (fixes #4125)

512f76f

snoyberg added a commit that referenced this issue Jul 5, 2018

Use a hard-coded tool dependency map (fixes #4125)

ba9179e

snoyberg mentioned this issue Jul 5, 2018

'stack test --no-run-benchmarks' doesn't build the all benchmarks #4045

Open

snoyberg closed this as completed in #4132 Jul 9, 2018

snoyberg added a commit that referenced this issue Jul 9, 2018

Merge pull request #4132 from commercialhaskell/4125-cabal-style-buil…

93de6a9

…d-tools Use a hard-coded tool dependency map (fixes #4125)

mgajda mentioned this issue Jul 28, 2018

Global install of alex is missed when installing into Stack sandbox gtk2hs/gtk2hs#251

Open

snoyberg added a commit that referenced this issue Aug 13, 2018

Use a custom snapshot

9c592a6

This bumps us to newer versions of some libraries, in particular conduit, which were previously blocked by #4125. Using a custom snapshot should allow this by bypassing that bug.

Vonfry mentioned this issue Jan 16, 2019

Build failed on MacOS with clang link error(ghc 8.4.4) haskell/haskell-ide-engine#1058

Closed

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

stack 1.7.1 still has problems finding build tools ("The program 'happy' is required") #4125

stack 1.7.1 still has problems finding build tools ("The program 'happy' is required") #4125

simonmichael commented Jul 2, 2018 •

edited

Loading

mihaimaruseac commented Jul 2, 2018

simonmichael commented Jul 2, 2018 via email

simonmichael commented Jul 2, 2018

snoyberg commented Jul 4, 2018

snoyberg commented Jul 4, 2018

snoyberg commented Jul 4, 2018

simonmichael commented Jul 4, 2018

snoyberg commented Jul 4, 2018

simonmichael commented Jul 4, 2018

mihaimaruseac commented Jul 4, 2018

snoyberg commented Jul 5, 2018

simonmichael commented Jul 5, 2018 •

edited

Loading

snoyberg commented Jul 5, 2018

simonmichael commented Jul 5, 2018

mihaimaruseac commented Jul 5, 2018

stack 1.7.1 still has problems finding build tools ("The program 'happy' is required") #4125

stack 1.7.1 still has problems finding build tools ("The program 'happy' is required") #4125

Comments

simonmichael commented Jul 2, 2018 • edited Loading

General summary/comments (optional)

Steps to reproduce

Expected

Actual

Stack version

Method of installation

mihaimaruseac commented Jul 2, 2018

simonmichael commented Jul 2, 2018 via email

simonmichael commented Jul 2, 2018

snoyberg commented Jul 4, 2018

snoyberg commented Jul 4, 2018

snoyberg commented Jul 4, 2018

simonmichael commented Jul 4, 2018

snoyberg commented Jul 4, 2018

simonmichael commented Jul 4, 2018

mihaimaruseac commented Jul 4, 2018

snoyberg commented Jul 5, 2018

simonmichael commented Jul 5, 2018 • edited Loading

snoyberg commented Jul 5, 2018

simonmichael commented Jul 5, 2018

mihaimaruseac commented Jul 5, 2018

simonmichael commented Jul 2, 2018 •

edited

Loading

simonmichael commented Jul 5, 2018 •

edited

Loading