jenkins hsbencher 7.10 failure

[svenssonjoel]

http://tester-lin.soic.indiana.edu:8080/job/HSBencher/JENKINS_GHC=7.10.1,label=linux-soic/1017/console

This fails. Seems to happen during tests rather than install. Install does look a bit funny though.

[tmcdonell]

Ryan just asked me to have a look at it. The log looks weird. I tried to
build manually and some of the components failed to install, so the log
might have picked up on the wrong error.

I just submitted a pull request that will fix the builds with 7.10
(although I didn't run the tests...)

On Thu, 21 May 2015 at 08:57 Joel Svensson notifications@github.com wrote:

http://tester-lin.soic.indiana.edu:8080/job/HSBencher/JENKINS_GHC=7.10.1,label=linux-soic/1017/console

This fails. Seems to happen during tests rather than install. Install does
look a bit funny though.

—
Reply to this email directly or view it on GitHub
#93.

[rrnewton]

This error is usually from switching cabal version (from pre 1.22 to 1.22):

[cabalMethod] Failed to install bench1-0.1
 [cabalMethod]  [stderr] ghc: ghc no longer supports single-file style package databases (dist/package.conf.inplace) use 'ghc-pkg init' to create the database with the correct format.
 [cabalMethod]  [stderr] cabal: Error: some packages failed to install:

But wiping out workspaces should be sufficient to fix that. Some jobs are set to automatically wipe workspaces when the job fails.

[rrnewton]

Ah, this job is wiping the workspace... but I think we're getting cabal skew even within the job.

On parfunc currently the default cabal executable is 1.20. But this job is set to explicitly use cabal-1.22 for GHC 7.10 support... and yet the hsbencher builds themselves just call "cabal", so somewhere in there I think we're using both 1.20 and 1.22 on the same directory.

(I had made the system wide default 1.22... but then ran into some other backwards compatibility problem that I'm forgetting right now. It would probably be good to have NO cabal in path and force jobs to select one explicitly or set up their paths.)

[rrnewton]

Actually -- here's one quick fix. I propose a new policy for paths management.

The specific directories with GHC binaries:

• ~/opt/ghc-7.10.1/bin
• ~/opt/ghc-7.8.4/bin
• etc

In addition to providing "ghc" and "ghci" we should also put appropriate versions of "cabal" (naked, no suffixes) in there. That way when we put ghc 7.10 in the path, cabal 1.22 automatically becomes the default. I did this just now for GHC 7.8 and 7.10. Let's see if it fixes that build. It's running now in build 1019.

[rrnewton]

Yep, looks like it worked.