Skip to content

test: add windows and c++ coverage #35670

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.

Sign up for GitHub

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

Closed
bcoe wants to merge 12 commits into from
Closed

test: add windows and c++ coverage #35670

Changes from 1 commit
Commits
Show all changes
12 commits
Select commit Hold shift + click to select a range
df981ea
test: add windows and C++ coverage
Oct 17, 2020
d91b81d
build: improve coverage configuration
Oct 18, 2020
656160f
chore: attempt to build with gcov
Oct 18, 2020
9eac50b
build: ensure gcovr tool exists
Oct 18, 2020
f869255
chore: tweak codecov.yml file
Oct 18, 2020
f5d6272
multi-line command had issues
Oct 18, 2020
40cb785
chore: delete more output files
Oct 18, 2020
fc7c05c
build: run test-cov rather than test-ci
Oct 18, 2020
5939514
chore: address review
Oct 20, 2020
71f998a
chore: fiddle with gcovr settings
Oct 20, 2020
15d170e
chore: simplify command
Oct 20, 2020
c646f6d
build: a couple more small tweaks to reports
Oct 20, 2020
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Prev Previous commit
Next Next commit
build: ensure gcovr tool exists
  • Loading branch information
bcoe
bcoe committed Oct 18, 2020
commit 9eac50be90c16e4a41df44bde9cc8494b682625f
6 changes: 6 additions & 0 deletions .github/workflows/coverage-linux.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -21,6 +21,12 @@ jobs:
python-version: ${{ env.PYTHON_VERSION }}
- name: Environment Information
run: npx envinfo
- name: Clone gcovr
run: git clone -b 3.4 --depth=1 --single-branch https://github.com/gcovr/gcovr.git
- name: Clone patch for gcovr

@bcoe bcoe Oct 18, 2020

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

@mhdawson do you remember why we're running gcovr from a branch and floating a patch? It would be nice to simplify this.

@mhdawson mhdawson Oct 19, 2020

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

It been long enough that I don't remember the specifics. I assume it failed to run properly with out that patch. It's possible a later version of gcovr may have fixed it.

@bcoe bcoe Oct 20, 2020

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

@mhdawson I've managed to get gcovr@4.2 working, installed directly from pip.

The trick was to continue running from the out/ folder, but to specify a --root pointing to the root project directory.

run: git clone --depth=1 --single-branch https://github.com/nodejs/build.git
- name: Patch gcovr
run: cd gcovr && patch -N -p1 < ../build/jenkins/scripts/coverage/gcovr-patches-3.4.diff
- name: Build
run: make build-ci -j2 V=1 CONFIG_FLAGS="--error-on-warn --coverage"
# TODO(bcoe): fix the couple tests that fail with the inspector enabled.
Expand Down