Setup continuous integration about openfast HOT 7 CLOSED

Hi @rafmudaf

I would recommend to put the task element all in the first comments so they get recognized by Github

from openfast.

@petebachant do you know of any resources for compiling fortran on Travis CI?

Ive set up a Travis CI account but haven't found info on working around the lack of fortran support.

from openfast.

If you're running the tests on an Ubuntu machine (default I believe), installing gfortran should be as easy as adding this to .travis.yml:

before_install:
    - sudo apt-get update -qq
    - sudo apt-get install -qq gfortran

from openfast.

At the moment, running the regression test suite in a continuous integration environment is impractical due to the time required to run all tests. Some options for reducing the length of the regression test:

• Shorten the simulation times
• Start from a restart file
• Run a subset of the tests

from openfast.

TravisCI now supports Windows in beta, so I've set up a preliminary Windows build. There are also hacks for getting an intel compiler on the TravisCI container. There is an existing bug which prevents the Windows container from properly launching when a secret is included in the TravisCI configuration and a secret is required to pass the Intel Fortran license serial number.

The long regression test issue still persists.

from openfast.

Builds to test

• Mac - gfortran - single precision
• Mac - gfortran - double precision
• Linux - gfortran - single precision
• Linux - gfortran - double precision
• Linux - ifort - single precision
• Linux - ifort - double precision
• Windows - ifort - single precision
• Windows - ifort - double precision
• Windows with cygwin

Tests to test

• Regression tests
• Unit tests
• A memory test would be cool

from openfast.

Closing the practical targets are covered and the impractical ones (i.e. Windows + CygWin) probably won't be. Also, see https://github.com/OpenFAST/openfast/projects/2.

from openfast.