Skip to content

add code coverage workflow #71

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

Merged
merged 10 commits into from
Jan 24, 2025
Merged

add code coverage workflow #71

merged 10 commits into from
Jan 24, 2025

Conversation

imor
Copy link
Contributor

@imor imor commented Jan 23, 2025

Adds a new code coverage workflow to send code coverage to coveralls

@imor imor marked this pull request as ready for review January 23, 2025 07:43
with:
github-token: ${{ secrets.GITHUB_TOKEN }}
path-to-lcov: lcov.info
debug: true
Copy link

Choose a reason for hiding this comment

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

I guess git doesn't like it when you don't have a newline at end of file.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Added a newline

sudo chmod a+rwx `/usr/lib/postgresql/16/bin/pg_config --pkglibdir` `/usr/lib/postgresql/16/bin/pg_config --sharedir`/extension /var/run/postgresql/

- run: cargo install cargo-pgrx --version 0.12.6
- run: cargo pgrx init --pg16 /usr/lib/postgresql/16/bin/pg_config
Copy link

Choose a reason for hiding this comment

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

Will it matter if this code coverage check is only done on pg 16 but that our targets are pg15 and 17 downstream?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

No, it shouldn't matter because this is just generating code coverage which for all practical purposes will be the same whichever pg version we use here.

Copy link

@samrose samrose left a comment

Choose a reason for hiding this comment

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

I guess git doesn't like it when you don't have a newline at end of file.

@imor imor merged commit 76d5779 into master Jan 24, 2025
3 checks passed
@imor imor deleted the code-coverage branch January 24, 2025 09:19
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.

2 participants