Varosi appveyor #1361

ranjitjhala · 2018-10-11T15:57:34Z

A new PR applying @varosi 's appveyor changes to the latest develop.

… any problem is found it must be related to exact GIT commit.

ranjitjhala · 2018-10-11T16:29:40Z

Hi @varosi -- looks like rebasing against the latest develop helps with circle. However, the appveyor builds are failing for two reasons:

the long file names?
somehow HsColour is not getting built due to some tab/spaces issue?

For 2 is it possible to disable that warning in the appveyor script?
~~For 1 we could potentially split those giant "log" files into some separate repo? Would that help?~~

~~EDIT: actually looks like your renaming of the files was not applied in the PR. Hmm. Maybe I can just do it manually...~~

Actually looks like it was applied in the PR but somehow the appveyor build is still trying to checkout the files:

error: unable to create file tests/logs/regrtest_results_goto_Fri_Sep_21_17:19:54_2012: Invalid argument
error: unable to create file tests/logs/regrtest_results_goto_Mon_Feb__4_08:25:21_2013: Invalid argument
error: unable to create file tests/logs/regrtest_results_goto_Mon_Oct_22_15:45:04_2012: Invalid argument
error: unable to create file tests/logs/regrtest_results_goto_Mon_Oct_22_20:52:56_2012: Invalid argument
error: unable to create file tests/logs/regrtest_results_goto_Sat_Feb_23_18:38:19_2013: Invalid argument
error: unable to create file tests/logs/regrtest_results_goto_Sun_Jan_13_17:11:09_2013: Invalid argument
error: unable to create file tests/logs/regrtest_results_goto_Sun_Jul_13_22:12:12_2014_post_errormsg_parseparens: Invalid argument
error: unable to create file tests/logs/regrtest_results_goto_Sun_Oct_28_17:24:34_2012: Invalid argument
error: unable to create file tests/logs/regrtest_results_goto_Wed_Nov_20_15:28:50_2013-master: Invalid argument
error: unable to create file tests/logs/regrtest_results_nikiL_Fri_Mar_29_12:56:37_2013: Invalid argument
error: unable to create file tests/logs/regrtest_results_ubuntu_Fri_Jul_29_17:38:55_2011: Invalid argument
error: unable to create file tests/logs/regrtest_results_ubuntu_Mon_Dec__5_03:32:39_2011: Invalid argument
error: unable to create file tests/logs/regrtest_results_ubuntu_Sun_Sep_11_15:52:57_2011: Invalid argument
error: unable to create file tests/logs/regrtest_results_ubuntu_Sun_Sep_11_19:38:55_2011: Invalid argument
error: unable to create file tests/logs/regrtest_results_ubuntu_Sun_Sep_11_20:12:06_2011: Invalid argument
error: unable to create file tests/logs/regrtest_results_ubuntu_Thu_Dec_22_02:51:46_2011: Invalid argument
error: unable to create file tests/logs/regrtest_results_ubuntu_Tue_Jul_19_10:07:18_2011: Invalid argument
error: unable to create file tests/logs/regrtest_results_ubuntu_Wed_Dec_21_03:11:45_2011: Invalid argument
error: unable to create file tests/logs/regrtest_results_ubuntu_Wed_Dec_21_03:14:29_2011: Invalid argument
error: unable to create file tests/logs/regrtest_results_ubuntu_Wed_Dec_21_16:45:26_2011: Invalid argument
error: unable to create file tests/logs/regrtest_results_ubuntu_Wed_Dec_21_18:09:31_2011: Invalid argument
error: unable to create file tests/logs/regrtest_results_ubuntu_Wed_Dec_21_18:42:19_2011: Invalid argument
error: unable to create file tests/logs/regrtest_results_ubuntu_Wed_Dec_21_19:13:26_2011: Invalid argument
error: unable to create file tests/logs/regrtest_results_ubuntu_Wed_Dec_21_19:14:10_2011: Invalid argument
error: unable to create file tests/logs/regrtest_results_ubuntu_Wed_Sep__7_14:45:19_2011: Invalid argument
fatal: unable to checkout working tree
warning: Clone succeeded, but checkout failed.

Any idea why?

Thanks!

varosi · 2018-10-11T21:34:29Z

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.

varosi · 2018-10-11T21:47:29Z

It's interesting that problem in hscolor is in it, not in liquidhaskell:

C:\tmp\stack2544\hscolour-1.24.4\Language\Haskell\HsColour.hs:37:19: warning: [-Wtabs]
280 Tab character found here, and in two further locations.
281 Please use spaces instead.
282 |
283 37 | -> String -- ^ Title for output.
284 | ^^^^^^
285 ignoring (possibly broken) abi-depends field for packages
286

Something in the new LTS I think. We could try with some other version of it.

ranjitjhala · 2018-10-11T21:50:20Z

I disabled the tabs warning to make progress, but its getting stuck on something else, c.f.

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?

varosi · 2018-10-17T19:10:17Z

I tried this: https://www.appveyor.com/docs/how-to/rdp-to-build-worker/
It works well, but only from Windows machine doing remote desktop.
You could cherry pick latest commit (33fe462ed5446e805f78e09ff4a44b3302c9b642) on my branch to enable RDP.
One problem is that the VM is live only 60min. On my tests it is even less.

varosi · 2018-10-17T19:26:58Z

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?

ranjitjhala · 2018-10-17T19:42:22Z

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> .

varosi · 2018-10-18T16:34:35Z

@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.

varosi · 2018-10-23T23:04:40Z

haskell/cabal#5465

varosi · 2018-10-23T23:05:37Z

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

varosi · 2018-12-16T19:02:11Z

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?

ranjitjhala · 2018-12-17T00:49:19Z

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> .

nikivazou · 2018-12-17T07:59:44Z

Yes! 8.6 is the stable current release!

varosi · 2018-12-17T09:37:49Z

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.

varosi · 2018-12-24T09:43:00Z

Happy LTS! Now with GHC 8.6.3
https://www.stackage.org/lts-13.0

ranjitjhala · 2018-12-29T16:40:39Z

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> .

varosi · 2018-12-29T21:58:15Z

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> .

varosi · 2018-12-29T22:10:39Z

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> > . >

nikivazou · 2019-03-26T18:12:40Z

So, hopefully windows build is fixed with our upgrade!

ranjitjhala · 2019-03-26T18:20:14Z

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> .

nikivazou · 2019-03-26T18:39:55Z

In the comments @varosi said there is a fix in ghc-8.6

varosi · 2019-03-26T19:03:40Z

Yes, I have tested with GHC-8.6 before.
So now LiquidHaskell use GHC-8.6! Yay! I'll test it

ranjitjhala · 2019-03-26T19:13:45Z

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> .

varosi · 2019-04-01T17:04:42Z

#1442

varosi added 30 commits October 9, 2018 01:20

Initial AppVeyor config

65c220d

Use name that is recognized by the service

889b0ed

Use install section

872fcd9

Test Stack install

6cf08f0

Git issue workaround

af2313b

Build status icon

177ee09

Build status icon #2

2b286a7

Check GIT version

1e8dfe4

Remove GIT install

17715e3

Try to fix GIT problem on Windows

00e66ab

Remove colons from file names which are not supported on Windows

774be0a

Directly rename files

389d309

Remove a file for a test

a7f751c

Enable stack test

2a6f970

git submodule update

9943d57

Some cleanup

08cc23c

Fix path

5e9588c

Fix path - no

611563a

Install Microsoft Z3 from NuGet

6f939e0

Added build step and removed temporarily NuGet version argument

2ccf496

Add nuget restore to restore missing packages

4e475f9

Try without Restore

f99f544

Use exact version of Z3 which must be tracked with GIT commits. So if…

a5d4ab7

… any problem is found it must be related to exact GIT commit.

Add dir commands to check which artefacts are installed

4a3d7f3

Add artifacts archiving

bf80d38

Test if Z3 is really accessible

33d3f9b

Use Z3 package that has an executable

4987010

Add Z3 to PATH

ec98763

Improved logging

34d3b2d

Fix a problem with YAML

8fa45d4

ranjitjhala added 4 commits October 11, 2018 09:33

remove wouter-xmonad

9e9be1f

add no-warns-tabs

b80559d

disable tab-warning for hscolor

414bcf5

disable all-warnings for hscolor

d015466

nikivazou closed this Mar 26, 2019

nikivazou deleted the varosi-appveyor branch June 10, 2019 10:42

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Varosi appveyor #1361

Varosi appveyor #1361

ranjitjhala commented Oct 11, 2018

ranjitjhala commented Oct 11, 2018 •

edited

Loading

varosi commented Oct 11, 2018 •

edited

Loading

varosi commented Oct 11, 2018 •

edited

Loading

ranjitjhala commented Oct 11, 2018

varosi commented Oct 17, 2018 •

edited

Loading

varosi commented Oct 17, 2018 •

edited

Loading

ranjitjhala commented Oct 17, 2018 via email

varosi commented Oct 18, 2018

varosi commented Oct 23, 2018

varosi commented Oct 23, 2018 •

edited

Loading

varosi commented Dec 16, 2018 •

edited

Loading

ranjitjhala commented Dec 17, 2018 via email

nikivazou commented Dec 17, 2018

varosi commented Dec 17, 2018 •

edited

Loading

varosi commented Dec 24, 2018

ranjitjhala commented Dec 29, 2018 via email

varosi commented Dec 29, 2018 via email

varosi commented Dec 29, 2018 via email

nikivazou commented Mar 26, 2019

ranjitjhala commented Mar 26, 2019 via email

nikivazou commented Mar 26, 2019

varosi commented Mar 26, 2019

ranjitjhala commented Mar 26, 2019 via email

varosi commented Apr 1, 2019

Varosi appveyor #1361

Varosi appveyor #1361

Conversation

ranjitjhala commented Oct 11, 2018

ranjitjhala commented Oct 11, 2018 • edited Loading

varosi commented Oct 11, 2018 • edited Loading

varosi commented Oct 11, 2018 • edited Loading

ranjitjhala commented Oct 11, 2018

varosi commented Oct 17, 2018 • edited Loading

varosi commented Oct 17, 2018 • edited Loading

ranjitjhala commented Oct 17, 2018 via email

varosi commented Oct 18, 2018

varosi commented Oct 23, 2018

varosi commented Oct 23, 2018 • edited Loading

varosi commented Dec 16, 2018 • edited Loading

ranjitjhala commented Dec 17, 2018 via email

nikivazou commented Dec 17, 2018

varosi commented Dec 17, 2018 • edited Loading

varosi commented Dec 24, 2018

ranjitjhala commented Dec 29, 2018 via email

varosi commented Dec 29, 2018 via email

varosi commented Dec 29, 2018 via email

nikivazou commented Mar 26, 2019

ranjitjhala commented Mar 26, 2019 via email

nikivazou commented Mar 26, 2019

varosi commented Mar 26, 2019

ranjitjhala commented Mar 26, 2019 via email

varosi commented Apr 1, 2019

ranjitjhala commented Oct 11, 2018 •

edited

Loading

varosi commented Oct 11, 2018 •

edited

Loading

varosi commented Oct 11, 2018 •

edited

Loading

varosi commented Oct 17, 2018 •

edited

Loading

varosi commented Oct 17, 2018 •

edited

Loading

varosi commented Oct 23, 2018 •

edited

Loading

varosi commented Dec 16, 2018 •

edited

Loading

varosi commented Dec 17, 2018 •

edited

Loading