Skip to content
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

Moved CI to GH Actions. #14

Merged
merged 9 commits into from Aug 18, 2021
Merged

Moved CI to GH Actions. #14

merged 9 commits into from Aug 18, 2021

Conversation

MSallermann
Copy link
Member

Replaces the travis and appveyor CI with github actions.
Includes coverage and pypi deployment and also adds windows builds, which were previously not covered.
Branched from master, since it is ahead of develop.

Copy link
Member

@GPMueller GPMueller left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Aside from the Fortran build missing, this looks very good 👍

.github/workflows/ci.yml Outdated Show resolved Hide resolved
.github/workflows/ci.yml Outdated Show resolved Hide resolved
.github/workflows/ci.yml Outdated Show resolved Hide resolved
.github/workflows/ci.yml Outdated Show resolved Hide resolved
@GPMueller
Copy link
Member

I'm not sure why the codecov comment and checks are missing, but I activated the coveralls comment and set a minimum of 80% coverage for success and a max. 5% coverage decrease.
I also removed the AppVeyor connection so the CI should work fine from the next run onwards.

@codecov
Copy link

codecov bot commented Aug 12, 2021

Codecov Report

❗ No coverage uploaded for pull request base (master@d5e3e07). Click here to learn what that means.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master      #14   +/-   ##
=========================================
  Coverage          ?   52.22%           
=========================================
  Files             ?        8           
  Lines             ?     1779           
  Branches          ?        0           
=========================================
  Hits              ?      929           
  Misses            ?      850           
  Partials          ?        0           

@MSallermann MSallermann force-pushed the gh_actions branch 6 times, most recently from a7ee7a9 to e0b87de Compare August 12, 2021 07:57
@MSallermann
Copy link
Member Author

MSallermann commented Aug 12, 2021

I think I made all the requested changes.
The test of the fortran bindings seems to fail on the debug build, however. I think this might be a genuine bug.

https://github.com/spirit-code/ovf/pull/14/checks?check_run_id=3309330205

At line 118 of file /home/runner/work/ovf/ovf/fortran/ovf.f90
5: Fortran runtime error: Substring out of bounds: upper bound (72) of 'f_ptr' exceeds string length (0)

Copy link
Member

@GPMueller GPMueller left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks like coveralls should be called a little differently. Right now, it is also calculating the coverage of the python/test folder: https://coveralls.io/github/spirit-code/ovf?branch=gh_actions
Looking at https://github.com/spirit-code/spirit/blob/develop/.github/workflows/ci.yml#L117-L126, I think the coverage call should be

coverage run --source ovf --omit=ovf/ovflib.py setup.py test > cov.txt

Moritz added 2 commits August 12, 2021 18:35
- removed superfluous openmp line
- added fortran build on ubuntu
- added rocket icon to deploy step name
- more consistent naming of steps
`c_f_pointer` does not assign a length to the ponted-to character string
 `f_ptr`, so that debug builds (with bounds checks) cause a "substring
 out of bounds" error when accessing `f_ptr` to assign it to `f_string`.

 `f_ptr` is now an array and `c_f_pointer` gets passed the shape that
 should be assigned. The array is then read into the `f_string` string
 in a do-loop.
@MSallermann MSallermann merged commit 6e3383e into master Aug 18, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants