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.

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

re-enable hakyll #5304

Merged
merged 1 commit into from
Apr 14, 2020
Merged

re-enable hakyll #5304

merged 1 commit into from
Apr 14, 2020

Conversation

simonmichael
Copy link
Contributor

@simonmichael
Copy link
Contributor Author

The CI failure involves ghc-lib-parser and ghc-syntax-highlighter, which aren't part of the hakyll test build I did locally. Would anyone know what causes those to be included ?

@simonmichael
Copy link
Contributor Author

simonmichael commented Apr 14, 2020

I think it's ghc-syntax-highlighter's fault (mrkkrp/ghc-syntax-highlighter#17), but still a little odd why stackage curator feels it needs the latest ghc-syntax-highlighter-0.6.0.0 from hackage instead of the 0.0.5.0@rev:3 that's in stackage (nightly-2020-04-13 at least; I can't see the nightly-2020-04-14 curator appears to be using).

@bergmark
Copy link
Member

@simonmichael curator checks against the latest version of all packages unless there are upper bounds in place. It might include things newer than what's published in nightly - this step also runs on the build server before we start the nigthly build, so we see that error there as well.
So, nothing you need to do.

@bergmark
Copy link
Member

Thanks!

@bergmark bergmark merged commit 4025569 into commercialhaskell:master Apr 14, 2020
@simonmichael
Copy link
Contributor Author

simonmichael commented Apr 14, 2020

Ok then! I suppose this provides useful advance warning for core stackage maintainers, but makes the CI a little confusing for everyday contributors.

@simonmichael
Copy link
Contributor Author

(And thanks.)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants