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
Update to LTS-11 #187
Update to LTS-11 #187
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for updating it!
I'm kicking off the tests.
stack.yaml
Outdated
@@ -16,12 +16,9 @@ packages: | |||
extra-deps: | |||
- snappy-framing-0.1.1 | |||
- snappy-0.2.0.2 | |||
# TODO: Remove these once the new versions are in lts-9. | |||
- haskell-src-exts-1.19.1 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can you add a comment explaining why we need an older version? e.g. name the module that needs to be updated
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@fkm3 Done!
I'm getting this error when I try it:
|
@fkm3 Looks like this is an issue with some older versions of stack. Can you try to upgrade |
That does fix it locally for me. The tests use the Dockerfile which gets stack from download.fpcomplete.com/ubuntu. Maybe that repo has an old version of stack. I'll look more closely later today if I get a chance. |
Required by tensorflow#187. The version we were using is old enough that it doesn't work with the latest stackage LTS. haskellstack.org says There is also a Ubuntu package for Ubuntu 16.10 and up, but the distribution's Stack version lags behind, ... So, instead of asking them to update it, it's probably better to download the tar of the version we want. Somehow updating stack surfaced a new pedantic warning in GradientTest, so I've fixed that as well (and cleanup some code using snake_case).
Required by tensorflow#187. The version we were using is old enough that it doesn't work with the latest stackage LTS. haskellstack.org says There is also a Ubuntu package for Ubuntu 16.10 and up, but the distribution's Stack version lags behind, ... So, instead of asking them to update it, it's probably better to download the tar of the version we want. Somehow updating stack surfaced a new pedantic warning in GradientTest, so I've fixed that as well (and cleaned up some code using snake_case).
Sent #189 to fix the stack version. |
How bad is it to jump to ghc 8.4 and the nightly stackage snapshot? If we are to experience the pain of the upgrade, might as well reduce the incidence (even at the increased intensity :) |
Required by #187. The version we were using is old enough that it doesn't work with the latest stackage LTS. haskellstack.org says There is also a Ubuntu package for Ubuntu 16.10 and up, but the distribution's Stack version lags behind, ... So, instead of asking them to update it, it's probably better to download the tar of the version we want. Somehow updating stack surfaced a new pedantic warning in GradientTest, so I've fixed that as well.
If you sync this to HEAD, then the CI tests should pass and we can merge it. @blackgnezdo, won't switching to nightly increase the incident? No opinion from me though :) |
I meant pick a dated snapshot of nightly. But I'm also somewhat ambivalent. Just throwing it out there. @ehamberg could you rebase to make sure your change is compatible with HEAD? |
@blackgnezdo Sure. Done. |
You still need to merge baa501b into this PR, otherwise the tests will fail. Thanks! |
Required by tensorflow#187. The version we were using is old enough that it doesn't work with the latest stackage LTS. haskellstack.org says There is also a Ubuntu package for Ubuntu 16.10 and up, but the distribution's Stack version lags behind, ... So, instead of asking them to update it, it's probably better to download the tar of the version we want. Somehow updating stack surfaced a new pedantic warning in GradientTest, so I've fixed that as well.
@fkm3 Ah. Missed that. Rebased on top of the latest |
I see some build errors tensorflow-mnist-0.1.0.0: Test suite ParseTest passed -- Dumping log file due to warnings: /tfhs/.stack-work/logs/tensorflow-records-conduit-0.1.0.0.log Configuring tensorflow-records-conduit-0.1.0.0... /tfhs/tensorflow-records-conduit/src/TensorFlow/Records/Conduit.hs:40:36: warning: [-Wdeprecations] /tfhs/tensorflow-records-conduit/src/TensorFlow/Records/Conduit.hs:44:67: warning: [-Wdeprecations] /tfhs/tensorflow-records-conduit/src/TensorFlow/Records/Conduit.hs:45:40: warning: [-Wdeprecations] /tfhs/tensorflow-records-conduit/src/TensorFlow/Records/Conduit.hs:48:31: warning: [-Wdeprecations] /tfhs/tensorflow-records-conduit/src/TensorFlow/Records/Conduit.hs:52:51: warning: [-Wdeprecations] /tfhs/tensorflow-records-conduit/src/TensorFlow/Records/Conduit.hs:53:38: warning: [-Wdeprecations] : error: -- End of log file: /tfhs/.stack-work/logs/tensorflow-records-conduit-0.1.0.0.log Log files have been written to: /tfhs/.stack-work/logs/ -- While building custom Setup.hs for package tensorflow-records-conduit-0.1.0.0 using:
[ID: 4581505] Build finished after 975 secs, exit value: 1 Warning: Permanently added 'localhost' (ECDSA) to the list of known hosts. |
@blackgnezdo Looks like it's failing due to deprecation warnings + |
- The `Conduit`, `Producer` and `Consumer` aliases are deprecated and `ConduitT` is used directly instead - `=$=` is deprecated and replaced by `.|`
@blackgnezdo I believe this is fixed now. |
@fkm3, I think we are good to merge this now? |
Thanks! |
Updates
stack.yaml
to use LTS-11 (GHC 8.2.2). Not sure if theTODO
should be kept.