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

Fails on macOS #13

Closed
paulz opened this issue Sep 2, 2019 · 8 comments
Closed

Fails on macOS #13

paulz opened this issue Sep 2, 2019 · 8 comments

Comments

@paulz
Copy link

paulz commented Sep 2, 2019

macOS build fails:

##[error]Container action is only supported on Linux

https://github.com/paulz/ImageCoordinateSpace/commit/4a8530e92f00011b1c8bf8cb1078676b1acc620c/checks#step:5:4

paulz added a commit to paulz/ImageCoordinateSpace that referenced this issue Sep 2, 2019
@adam7
Copy link

adam7 commented Sep 8, 2019

Also fails on Windows with the same error.

@adam7
Copy link

adam7 commented Sep 8, 2019

Build failure is because this is a Docker Action which are only supported on Linux. Porting to a JavaScript Action would resolve the issue because they are supported on Windows, macOS and Linux.

https://help.github.com/en/articles/about-actions#types-of-actions

baszalmstra added a commit to baszalmstra/mun that referenced this issue Oct 31, 2019
This commit replaces azure pipelines with github actions, tarpaulin with
(cross-platform) grcov, and codecov.io with coveralls.io.

Github Actions turned out to be a much better fit for this project. It
integrates much better with our already existing workflow, seems more
feature complete and is easier to work with.

Tarpaulin kept crashing on Azure Pipelines and after trying also with
Github Actions, its still under active development so thats not very
strange. However, I prefer to have inaccurate code coverage than no
coverage at all. Therefor I replaced Tarpaulin with grcov. grcov does
report some lines missed that are actually ok but again, its better than
nothing. Also, grcov works on all our target platforms so we get better
cross platform coverage in return.

I replaced codecov.io as our coverage service with coveralls.io.
Although I like the interface of codecov better there is no support
for uploading reports on macOS and windows. See
codecov/codecov-action#13 for more
information.
baszalmstra added a commit to baszalmstra/mun that referenced this issue Oct 31, 2019
This commit replaces azure pipelines with github actions, tarpaulin with
(cross-platform) grcov, and codecov.io with coveralls.io.

Github Actions turned out to be a much better fit for this project. It
integrates much better with our already existing workflow, seems more
feature complete and is easier to work with.

Tarpaulin kept crashing on Azure Pipelines and after trying also with
Github Actions, its still under active development so thats not very
strange. However, I prefer to have inaccurate code coverage than no
coverage at all. Therefor I replaced Tarpaulin with grcov. grcov does
report some lines missed that are actually ok but again, its better than
nothing. Also, grcov works on all our target platforms so we get better
cross platform coverage in return.

I replaced codecov.io as our coverage service with coveralls.io.
Although I like the interface of codecov better there is no support
for uploading reports on macOS and windows. See
codecov/codecov-action#13 for more
information.
baszalmstra added a commit to mun-lang/mun that referenced this issue Oct 31, 2019
This commit replaces azure pipelines with github actions, tarpaulin with
(cross-platform) grcov, and codecov.io with coveralls.io.

Github Actions turned out to be a much better fit for this project. It
integrates much better with our already existing workflow, seems more
feature complete and is easier to work with.

Tarpaulin kept crashing on Azure Pipelines and after trying also with
Github Actions, its still under active development so thats not very
strange. However, I prefer to have inaccurate code coverage than no
coverage at all. Therefor I replaced Tarpaulin with grcov. grcov does
report some lines missed that are actually ok but again, its better than
nothing. Also, grcov works on all our target platforms so we get better
cross platform coverage in return.

I replaced codecov.io as our coverage service with coveralls.io.
Although I like the interface of codecov better there is no support
for uploading reports on macOS and windows. See
codecov/codecov-action#13 for more
information.
@ibrahim0814
Copy link
Contributor

Hi all,

Copying my answer from #7 here:

Thank you for bringing this up. I've updated our README to reflect this particular caveat. GitHub currently allows us to build two types of Actions - Docker and JS. We decided to use a Docker action since it allows us to wrap our bash uploader because our bash uploader is the only uploader the Codecov staff actively maintains. Of course, this comes at the cost of sacrificing Windows and macOS build capabilities.

Perhaps in the future, we will support these other operating systems, but for the time being, I do apologize that this action's functionality is limited to only Linux

Ib

@adam7
Copy link

adam7 commented Nov 12, 2019

Looking at your entrypoint https://github.com/codecov/codecov-action/blob/master/entrypoint.sh all your container does is download and then run a binary which you could just as easily do in a JavaScript Action and would give you cross platform support.

@ibrahim0814
Copy link
Contributor

@adam7 I'll look this, I wasn't aware that it was possible but perhaps my assumptions are incorrect here.

@nklayman
Copy link

Maybe you should add if: runner.os == 'Linux' to the readme example for now.

@ibrahim0814
Copy link
Contributor

@nklayman I added that line to our readme on this commit

Thanks for the suggestion!

@ibrahim0814
Copy link
Contributor

Hi all,

As of release v1.0.4, we've officially switched to using JavaScript for our action. It is now supported on Linux, macOS, and Windows. Feel free to use it your macOS and matrix builds :D

@adam7 Thank you for your initial suggestion!

Ib

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

No branches or pull requests

4 participants