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

GitHub actions #125

Merged
merged 5 commits into from
May 18, 2021
Merged

GitHub actions #125

merged 5 commits into from
May 18, 2021

Conversation

ranocha
Copy link
Contributor

@ranocha ranocha commented May 8, 2021

I enabled GitHub actions for CI and Documenter. It would be good if someone with more access rights can check this and set the appropriate secrets/settings.

I want to add this to allow more reliable testing, e.g. to bump the compat bound of BenchmarkTools.jl (#124).

@ranocha
Copy link
Contributor Author

ranocha commented May 17, 2021

Bump. Is there any interest in this?

@KristofferC
Copy link
Collaborator

KristofferC commented May 17, 2021

Yes, thanks! I wonder, is there a way not to get 7 coveralls checks? It feels a bit excessive.

@ranocha
Copy link
Contributor Author

ranocha commented May 17, 2021

I wonder, is there a way not to get 7 coveralls checks? It feels a bit excessive.

I don't know... I would really like to get rid of the intermediate runs and only keep coverage/coveralls, but I couldn't find a way to achieve that...

@KristofferC
Copy link
Collaborator

Maybe we can switch to codecov then? That seems to only give one check. I think this: https://github.com/KristofferC/NearestNeighbors.jl/blob/2efd998b6bb74d175e6cbbe1c8bc8e775e502f0b/.github/workflows/CI.yml#L45-L48 is the relevant lines that need to be used.

Comment on lines +48 to +50
- uses: codecov/codecov-action@v1
with:
file: lcov.info
Copy link
Contributor Author

Choose a reason for hiding this comment

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

@KristofferC These lines enable Codecov - I guess somebody needs to enable Codecov on their website?

@ranocha
Copy link
Contributor Author

ranocha commented May 17, 2021

Maybe we can switch to codecov then? That seems to only give one check. I think this: https://github.com/KristofferC/NearestNeighbors.jl/blob/2efd998b6bb74d175e6cbbe1c8bc8e775e502f0b/.github/workflows/CI.yml#L45-L48 is the relevant lines that need to be used.

We observed that Codecov and Coveralls report different coverage percentages when collecting data from parallel Julia tests, see https://community.codecov.io/t/code-lines-wrongly-detected-as-executable-in-parallel-jobs-for-a-julia-project/1940. Thus, I think it might be worth keeping the additional information reported by Coveralls

@KristofferC
Copy link
Collaborator

These tests are not run in parallel so I think that is no worry.

I think codecov is already active because it has data for the latest commit: https://codecov.io/gh/JuliaCI/PkgBenchmark.jl/commit/21896fc9a4ff5d0d26db086aa7ed72a9f88b1cb9/

@ranocha
Copy link
Contributor Author

ranocha commented May 17, 2021

Is there anything left to do for me?

  • I would propose to keep Coveralls since additional information doesn't hurt.
  • Someone could enable the Codecov integration in PRs if desired (report of the bot).
  • Someone should disable Appveyor to remove the failing CI test.

@KristofferC
Copy link
Collaborator

I've removed AV and coveralls. Additional information does hurt if is too noisy.

Thanks for the help with this!

@KristofferC KristofferC merged commit ded8934 into JuliaCI:master May 18, 2021
ranocha added a commit to ranocha/PkgBenchmark.jl that referenced this pull request May 18, 2021
Since Coveralls was removed in JuliaCI#125, I removed the relevant badge from the README.md.
This was referenced May 18, 2021
DilumAluthge pushed a commit that referenced this pull request May 18, 2021
Since Coveralls was removed in #125, I removed the relevant badge from the README.md.
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

3 participants