Cabal-1.24 testsuite timing-out in lts7

[juhp]

I don't think this happened in Nightly but the Cabal-1.24.2.0 testsuite is timing out randomly in the LTS 7.13 build.

For now (for lts-7.13) I kept Cabal at 1.24.1.0 and cabal-install at 1.24.0.1, though it would be good to move to Cabal-1.24.2.0 since 1.24.1.0 contained an API change.

[juhp]

But stackage-curator doesn't even like Cabal-1.24.1.0 any more:

base-4.9.0.0 is out of bounds for:

• Cabal-1.24.1.0 (< 0 && >=4.5 && < 5 && -any). Mikhail Glushenkov mikhail.glushenkov@gmail.com @23Skidoo. @haskell. Used by:
  library, test-suite

So I am reluctantly letting the testsuite fail for now.

[23Skidoo]

@hvr blacklisted the 1.24.1.0 release by adding a >1 && <1 constraint on base (there was a PVP violation). Try the recently released 1.24.2.0.

[juhp]

Thanks, but 1.24.2.0 is the one whose testsuite was timing-out...

[hvr]

I'm btw quite surprised that the LTS snapshot uses a different Cabal version from the one that's bundled with GHC 8.0.1, so far I assumed that LTS snapshots would be synchronized to their respective GHC releases' boot libraries.

[phadej]

@hvr, but Cabal is upgradable package (ghc doesn't depend on it). IIRC the boot library restriction was lifted a bit at some point.

[hvr]

@phadej I see, I wasn't aware the Stackage policy changed.

PS: What are the current guarantees/invariants that hold between two consecutive snapshots, i.e. LTS m.x and LTS m.(x+1) ?

[23Skidoo]

@juhp

Thanks, but 1.24.2.0 is the one whose testsuite was timing-out...

There was only one new test case added in 1.24.2.0 (BuildTargetErrors), you can try disabling it.

[bergmark]

PS: What are the current guarantees/invariants that hold between two consecutive snapshots, i.e. LTS m.x and LTS m.(x+1) ?

As with nightly we stick with boot versions if it's required in order to depend on that library + ghc. Usually, a LTS major sticks with the same major version of all libraries throughout its lifetime. We have made exceptions for executables and for serious bugs where fixes require breaking changes.

[juhp]

Thanks @23Skidoo: I heard later from @snoyberg that this Cabal testsuite timeout happened before in Stackage LTS builds - it seems to be intermittent and random so hard to reproduce (but was happening several times in a row for me the other day). If you haven't had any other reports then perhaps it might be triggered somehow by the Stackage Buildsystem?

[23Skidoo]

@juhp CI (Travis) works fine for us on Linux, though we've been having some problems with timeouts on macOS lately.

[bergmark]

We can re-open this if it pops up again.