Skip to content

Add AppVeyor continuous integration#307

Closed
Chris00 wants to merge 4 commits intoocaml:trunkfrom
Chris00:trunk
Closed

Add AppVeyor continuous integration#307
Chris00 wants to merge 4 commits intoocaml:trunkfrom
Chris00:trunk

Conversation

@Chris00
Copy link
Member

@Chris00 Chris00 commented Nov 23, 2015

This enables AppVeyor to compile OCaml Win64. So far it chokes on

    sed -e '/\/\*/d' \
        -e '/^#/d' \
        -e 's/enum \(.*\) {/let names_of_\1 = [|/' \
        -e 's/.*};$$/ |]/' \
        -e 's/\([A-Z][A-Z_0-9a-z]*\)/"\1"/g' \
        -e 's/,/;/g' \

in Makefile.shared. Anybody has an idea? (I am a bit surprised as the Win64 compilation has obviously been tested.)

@tomjridge
Copy link

maybe

-e '/[/][*]/ d'

?

On 23 November 2015 at 19:39, Christophe Troestler <[email protected]

wrote:

This enables AppVeyor to compile OCaml Win64. So far it chokes
https://ci.appveyor.com/project/Chris00/ocaml/build/1.0.43#L743 on

sed -e '/\/\*/d' \
    -e '/^#/d' \        -e 's/enum \(.*\) {/let names_of_\1 = [|/' \        -e 's/.*};$$/ |]/' \        -e 's/\([A-Z][A-Z_0-9a-z]*\)/"\1"/g' \        -e 's/,/;/g' \

in Makefile.shared. Anybody has an idea? (I am a bit surprised as the

Win64 compilation has obviously been tested.)

You can view, comment on, or merge this pull request online at:

#307
Commit Summary

  • Add AppVeyor continuous integration

File Changes

Patch Links:


Reply to this email directly or view it on GitHub
#307.

@Chris00
Copy link
Member Author

Chris00 commented Nov 23, 2015

@tomjridge This works, thanks. Still wondering why the previous version fails — it has been in place since the beginning and some people have compiled it on Windows before...

@Chris00 Chris00 force-pushed the trunk branch 10 times, most recently from 3f5d398 to 4657439 Compare November 25, 2015 07:39
@Chris00
Copy link
Member Author

Chris00 commented Nov 25, 2015

AppVeyor is green. Is there any interest in this continuous integration possibility (likely tweaking the current script which is minimal). It can also produce artifacts which may possibly be used to automatically generate Windows packages upon successful compilation.

@avsm
Copy link
Member

avsm commented Nov 25, 2015

We use Appveyor in several other contexts; I am happy to activate it as a paid account on ocaml/ocaml if this is merged.

@Chris00 Chris00 force-pushed the trunk branch 2 times, most recently from 7c9316f to 1897b07 Compare November 29, 2015 11:24
@gasche
Copy link
Member

gasche commented Nov 29, 2015

We have some testing running on Windows machine on the INRIA continuous integration platform (ci.inria.fr/ocaml). I would be in favor of integrating the weird quoting stuff (I suppose it is for paths with spaces in them?) and fixing the sed script if it is problematic in some cases, but I'm not personally very excited about burning more CPU somewhere in the world on each pull-request. (No strong opposition either, though.)

@Chris00
Copy link
Member Author

Chris00 commented Nov 30, 2015

I have started work elsewhere to have an easy way to make Win64 OCaml available for AppVeyor testing. Integrating the quoting stuff (needed indeed for paths with spaces) would be nice as I have to patch the sources ATM.

@chambart
Copy link
Contributor

chambart commented Dec 1, 2015

@gasche I think that like travis, this is quite important to make pull request management lighter since almost nobody (except Alain) test his patches on windows before submitting.

@alainfrisch
Copy link
Contributor

Yes, and even some core developers don't follow INRIA's CI feedback. I'm fully in favor of these extra tests.

@avsm I thought AppVeyor was free for open source projects.

@shayne-fletcher
Copy link
Contributor

I've had problems with this before. The issue turned out to be a MinGW
'sed' executable in the path instead of the Cygwin version.

On Mon, Nov 23, 2015 at 2:39 PM, Christophe Troestler <
[email protected]> wrote:

This enables AppVeyor to compile OCaml Win64. So far it chokes
https://ci.appveyor.com/project/Chris00/ocaml/build/1.0.43#L743 on

sed -e '/\/\*/d' \
    -e '/^#/d' \        -e 's/enum \(.*\) {/let names_of_\1 = [|/' \        -e 's/.*};$$/ |]/' \        -e 's/\([A-Z][A-Z_0-9a-z]*\)/"\1"/g' \        -e 's/,/;/g' \

in Makefile.shared. Anybody has an idea? (I am a bit surprised as the

Win64 compilation has obviously been tested.)

You can view, comment on, or merge this pull request online at:

#307
Commit Summary

  • Add AppVeyor continuous integration

File Changes

Patch Links:


Reply to this email directly or view it on GitHub
#307.

Shayne Fletcher

@Chris00
Copy link
Member Author

Chris00 commented Dec 3, 2015

@shayne-fletcher I checked and %CYG_ROOT%/bin/bash -lc "sed --version" reports:

/usr/bin/sed (GNU sed) 4.2.2
Copyright (C) 2012 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>.
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.

Written by Jay Fenlason, Tom Lord, Ken Pizzini,
and Paolo Bonzini.
GNU sed home page: <http://www.gnu.org/software/sed/>.
General help using GNU software: <http://www.gnu.org/gethelp/>.
E-mail bug reports to: <[email protected]>.
Be sure to include the word ``sed'' somewhere in the ``Subject:'' field.

Odd.

@bschommer
Copy link
Contributor

A simple way to avoid this problems is to reset the path to only point to cygwin before starting the script.

@Chris00 Chris00 force-pushed the trunk branch 4 times, most recently from 0dd4ec3 to 01d4883 Compare December 4, 2015 14:06
@Chris00
Copy link
Member Author

Chris00 commented Dec 4, 2015

I added make tests. They currently fail. Is this the right way of running the tests on Windows?

@gasche
Copy link
Member

gasche commented Dec 17, 2015

Well if we think the extra testing is useful then we should merge it as soon as possible.

@damiendoligez damiendoligez added this to the 4.03.0 milestone Dec 23, 2015
@mshinwell
Copy link
Contributor

@Chris00 Please make the fix Damien requested about && in Makefile.nt. Then we can merge this.

@mshinwell
Copy link
Contributor

@Chris00 And please resolve the merge conflict(s).

@damiendoligez
Copy link
Member

About sed versions, see also http://caml.inria.fr/mantis/view.php?id=5991
There is something fishy about some versions of sed 4.2.2, and the FSF web site lists 4.2.1 as the latest version.

@damiendoligez damiendoligez self-assigned this Feb 10, 2016
@damiendoligez
Copy link
Member

Merged (commit 37edba7).

@damiendoligez damiendoligez changed the title [WIP] Add AppVeyor continuous integration Add AppVeyor continuous integration Feb 10, 2016
@damiendoligez
Copy link
Member

@Chris00 I just noticed this PR contains enough code to be over the threshold, so could you please sign and return the CLA? Instructions are here: #342 (comment)

Thanks.

gasche added a commit to gasche/ocaml that referenced this pull request Feb 12, 2016
This summarizes Xavier's recommendations at
  ocaml#342 (comment)
which were later reused at
  ocaml#307 (comment)

In particular this should create a URL anchor to direct people to:
gasche added a commit to gasche/ocaml that referenced this pull request Feb 12, 2016
@damiendoligez
Copy link
Member

@Chris00 ping?

@Chris00
Copy link
Member Author

Chris00 commented Feb 24, 2016

I intend to sign it but, as I need my employer permission, I am waiting for his answer (the question already went through 3 administrative services, each one sending it to the next...).

@damiendoligez
Copy link
Member

So it's in progress. Good!

Octachron pushed a commit to Octachron/ocaml that referenced this pull request Feb 29, 2016
nojb pushed a commit to nojb/ocaml that referenced this pull request Jun 2, 2016
mshinwell pushed a commit to mshinwell/ocaml that referenced this pull request Feb 12, 2021
…eturn-type

Introduce Simplify_named_result
chambart pushed a commit to chambart/ocaml-1 that referenced this pull request Jan 4, 2022
EmileTrotignon pushed a commit to EmileTrotignon/ocaml that referenced this pull request Jan 12, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.