-
Notifications
You must be signed in to change notification settings - Fork 139
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
Varosi appveyor #1361
Varosi appveyor #1361
Conversation
… any problem is found it must be related to exact GIT commit.
Hi @varosi -- looks like rebasing against the latest
For 2 is it possible to disable that warning in the appveyor script?
Actually looks like it was applied in the PR but somehow the appveyor build is still trying to checkout the files:
Any idea why? Thanks! |
Great about CircleCI! Problems with "Invalid agrument" are because of colons (":") in file names. In my branch (commit a992e59) I have renamed them to not have colons. It's strange that they are still present. |
It's interesting that problem in hscolor is in it, not in liquidhaskell:
Something in the new LTS I think. We could try with some other version of it. |
I disabled the https://ci.appveyor.com/project/ranjitjhala/liquidhaskell/builds/19440719 Do you know if it is possible to "log onto" the VM to inspect the log to see what the problem is? |
I tried this: https://www.appveyor.com/docs/how-to/rdp-to-build-worker/ |
It's strange... your branch is building fine on my Windows machine. May be it's something with the VM. Could you restart the build? |
Hmm... yes so there must be something odd going on in the appveyor vm?
…On Wed, Oct 17, 2018 at 12:27 PM varosi ***@***.***> wrote:
It's strange that your branch is building fine on my Windows machine.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#1361 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ABkuOCqLaHVtXsP-89xq-w3eRTNMi_Cuks5ul4SDgaJpZM4XX3DJ>
.
|
@ranjitjhala, could you restart the CI? or push something to your branch so it try to rebuild? I don't have rights to push to that branch on your repo. |
I have reproduced the error at my AppVeyor instance, so I'll try to fight it by myself - https://ci.appveyor.com/project/varosi/liquidhaskell/builds/19737975 |
I hit a bad error on AppVeyor using GHC 8.4 - commercialhaskell/stack#4441 This problem is fixed in GHC 8.6. liquid-fixpoint module is building with 8.6 just fine. But building liquidhaskell itself rises lot of errors which are not trivial for me to fix without deep knowledge on LiquidHaskell. @ranjitjhala, do you have plans to make it build with 8.6? |
Sure is 8.6 pretty stable now? Would be good to upgrade.
…On Sun, Dec 16, 2018 at 11:02 AM varosi ***@***.***> wrote:
I hit a bad error on AppVeyor using GHC 8.4 - commercialhaskell/stack#4441
<commercialhaskell/stack#4441> This problem is
fixed in GHC 8.6. liquid-fixpoint module is building with 8.6 just fine.
But building liquidhaskell rises a lot of errors which are not trivial for
me to fix without deep knowledge on LiquidHaskell.
@ranjitjhala <https://github.com/ranjitjhala>, do you have plans to make
it build with 8.6?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#1361 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ABkuOLOdRgPKSWVK0HXl76N7yJhKrvgeks5u5pi0gaJpZM4XX3DJ>
.
|
Yes! 8.6 is the stable current release! |
It's stable as @nikivazou said, all tests on all libraries in current Stackage nightly are passing on three OSes. And it's close to release of LTS. As I know they don't do additional tests except those that are made on nightly bases automatically. GHC compiler is updated twice after the official release and soon we'll have it in LTS 13. |
Happy LTS! Now with GHC 8.6.3 |
Hi @varosi -- so if/when we move to GHC 8.6.3 then this should work? Ranjit.
…On Mon, Dec 24, 2018 at 1:43 AM varosi ***@***.***> wrote:
Happy LTS! Now with GHC 8.6.3
https://www.stackage.org/lts-13.0
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#1361 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ABkuOPRULbiU_ThwxK9awzrxwiTVDXTYks5u8KGkgaJpZM4XX3DJ>
.
|
Yes, I have tried to build fixpoint on AppVeyor with latest GHC 8.6. There
is a fix for that exact problem.
На сб, 29.12.2018 г., 18:40 ч. Ranjit Jhala <notifications@github.com>
написа:
… Hi @varosi -- so if/when we move to GHC 8.6.3 then this should work?
Ranjit.
On Mon, Dec 24, 2018 at 1:43 AM varosi ***@***.***> wrote:
> Happy LTS! Now with GHC 8.6.3
> https://www.stackage.org/lts-13.0
>
> —
> You are receiving this because you were mentioned.
> Reply to this email directly, view it on GitHub
> <
#1361 (comment)
>,
> or mute the thread
> <
https://github.com/notifications/unsubscribe-auth/ABkuOPRULbiU_ThwxK9awzrxwiTVDXTYks5u8KGkgaJpZM4XX3DJ
>
> .
>
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#1361 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AFxXhvDwVhkf0QYCRnnK6aFaCI-3hr5kks5u95sIgaJpZM4XX3DJ>
.
|
In 8.6 there are other Windows fixes as well - for example problems with
long paths are fixed there.
На сб, 29.12.2018 г., 23:57 ч. Vassil Ognyanov Keremidchiev <
varosi@gmail.com> написа:
… Yes, I have tried to build fixpoint on AppVeyor with latest GHC 8.6. There
is a fix for that exact problem.
На сб, 29.12.2018 г., 18:40 ч. Ranjit Jhala ***@***.***>
написа:
> Hi @varosi -- so if/when we move to GHC 8.6.3 then this should work?
> Ranjit.
>
>
> On Mon, Dec 24, 2018 at 1:43 AM varosi ***@***.***> wrote:
>
> > Happy LTS! Now with GHC 8.6.3
> > https://www.stackage.org/lts-13.0
> >
> > —
> > You are receiving this because you were mentioned.
> > Reply to this email directly, view it on GitHub
> > <
> #1361 (comment)
> >,
> > or mute the thread
> > <
> https://github.com/notifications/unsubscribe-auth/ABkuOPRULbiU_ThwxK9awzrxwiTVDXTYks5u8KGkgaJpZM4XX3DJ
> >
> > .
> >
>
> —
> You are receiving this because you were mentioned.
> Reply to this email directly, view it on GitHub
> <#1361 (comment)>,
> or mute the thread
> <https://github.com/notifications/unsubscribe-auth/AFxXhvDwVhkf0QYCRnnK6aFaCI-3hr5kks5u95sIgaJpZM4XX3DJ>
> .
>
|
So, hopefully windows build is fixed with our upgrade! |
What is the cause of this sunny optimism :) ?
…On Tue, Mar 26, 2019 at 11:13 AM Niki Vazou ***@***.***> wrote:
So, hopefully windows build is fixed with our upgrade!
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#1361 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ABkuOBE9MJW-ItNeAFygZxTx0D9pSMxzks5vamMZgaJpZM4XX3DJ>
.
|
In the comments @varosi said there is a fix in ghc-8.6 |
Yes, I have tested with GHC-8.6 before. |
Thanks!!
…On Tue, Mar 26, 2019 at 12:05 PM varosi ***@***.***> wrote:
Yes, I have tested with GHC-8.6 before.
So now LiquidHaskell use GHC-8.6! Yay! I'll test it
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#1361 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ABkuOKkLhWf2xttcDvG_fuzqpJdnKchkks5vam8NgaJpZM4XX3DJ>
.
|
A new PR applying @varosi 's appveyor changes to the latest
develop
.