Uh oh!
There was an error while loading. Please reload this page.
test: add windows and c++ coverage - #35670
Conversation
aaa926e to
df981eaCompare| run: npx envinfo | ||
| - name: Clone gcovr reporter | ||
| run: git clone -b 3.4 --depth=1 --single-branch https://github.com/gcovr/gcovr.git | ||
| - name: Clone patch for gcovr |
There was a problem hiding this comment.
@mhdawson do you remember why we're running gcovr from a branch and floating a patch? It would be nice to simplify this.
There was a problem hiding this comment.
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.
There was a problem hiding this comment.
@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.
Uh oh!
There was an error while loading. Please reload this page.
bcoe
commented
Oct 18, 2020
@richardlau@Trott@watilde@mhdawson , I think this is ready for review:
Why the drop in coverage?This is the first time we've combined C++ and JavaScript coverage, and our C++ coverage is a bit below the JavaScript thresholds -- I also noticed that codecov.io's numbers are a bit lower than our uploaded reports, I think this is because it treats partial line misses the same as misses. What's nextOnce this has been running for a week or two, and we're happy, I think we should:
|
Uh oh!
There was an error while loading. Please reload this page.
mhdawson
commented
Oct 19, 2020
mhdawson
commented
Oct 19, 2020
Does |
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
bcoe
commented
Oct 20, 2020
@mhdawson did you manage to open the reports? perhaps I can open an issue with codecov.io independently of this PR, since I don't believe this behavior is new. I've noticed myself in the past, that when looking at Node.js' nightly reports, I sometimes get prompted to authenticate -- I wonder if it happens to folks who have a prior session with codecov.io that's expired. |
| "html", | ||
| "text", | ||
| "lcov" | ||
| "cobertura" |
There was a problem hiding this comment.
I'm hoping this gives us better partial coverage (I noticed C++ reports branch level coverage).
targos
commented
Oct 20, 2020
@bcoe It also asks me to authenticate, even in an incognito window. |
@thomasrockhu sorry to keep bothering you (I think we're on the right track to getting this configured appropriately for the project). Folks are reporting that codecov.io is prompting them to authenticate to see the public reports:
Ideally there'd never be an authentication step for our users to view detailed reports, as the Node.js project is open source. Is there a configuration setting I'm missing? |
bcoe
commented
Oct 20, 2020
@targos@mhdawson is the authentication issue a blocker, or is it okay if I open a tracking issue on codecov.io? I seem to not be getting the authentication screen myself, either in an incognito window, or in another browser -- but, I have seen the behavior you're describing before -- I was hoping it was a bug that had been addressed, since I haven't been seeing a login prompt myself. |
targos
commented
Oct 20, 2020
It's not a blocker to me |
mhdawson
commented
Oct 21, 2020
Thanks for following up on the auth. As long as its not something that will be required long term it's not a blocker for me. |
This comment has been minimized.
This comment has been minimized.
nodejs-github-bot
commented
Oct 21, 2020
bcoe
commented
Oct 22, 2020
Landed in 7657f62 |
Collect Windows and C++ coverage. Configure codecov so that comments are more concise and are only left when coverage varies. PR-URL: #35670Fixes: #35696 Refs: #35653 Refs: #35646 Reviewed-By: Rich Trott <rtrott@gmail.com> Reviewed-By: Antoine du Hamel <duhamelantoine1995@gmail.com> Reviewed-By: Richard Lau <rlau@redhat.com> Reviewed-By: Jiawen Geng <technicalcute@gmail.com> Reviewed-By: Michael Dawson <midawson@redhat.com>
Hi @bcoe, I noticed you opened this ticket so I'll address the issue there. Users shouldn't be seeing any problems viewing open source reports, so there's definitely an issue. Thanks for raising it up! |
Collect Windows and C++ coverage. Configure codecov so that comments are more concise and are only left when coverage varies. PR-URL: #35670Fixes: #35696 Refs: #35653 Refs: #35646 Reviewed-By: Rich Trott <rtrott@gmail.com> Reviewed-By: Antoine du Hamel <duhamelantoine1995@gmail.com> Reviewed-By: Richard Lau <rlau@redhat.com> Reviewed-By: Jiawen Geng <technicalcute@gmail.com> Reviewed-By: Michael Dawson <midawson@redhat.com>
Collect Windows and C++ coverage. Configure codecov so that comments are more concise and are only left when coverage varies. PR-URL: #35670Fixes: #35696 Refs: #35653 Refs: #35646 Reviewed-By: Rich Trott <rtrott@gmail.com> Reviewed-By: Antoine du Hamel <duhamelantoine1995@gmail.com> Reviewed-By: Richard Lau <rlau@redhat.com> Reviewed-By: Jiawen Geng <technicalcute@gmail.com> Reviewed-By: Michael Dawson <midawson@redhat.com>
Collect Windows and C++ coverage. Configure codecov so that comments are more concise and are only left when coverage varies. PR-URL: #35670Fixes: #35696 Refs: #35653 Refs: #35646 Reviewed-By: Rich Trott <rtrott@gmail.com> Reviewed-By: Antoine du Hamel <duhamelantoine1995@gmail.com> Reviewed-By: Richard Lau <rlau@redhat.com> Reviewed-By: Jiawen Geng <technicalcute@gmail.com> Reviewed-By: Michael Dawson <midawson@redhat.com>

Experiment to see if collecting coverage for Windows will "just work".
Refs: #35653
Refs: #35646
Fixes: #35696
Checklist
make -j4 test(UNIX), orvcbuild test(Windows) passes