-
Notifications
You must be signed in to change notification settings - Fork 109
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
Fix code coverage collection & reporting #1653
Fix code coverage collection & reporting #1653
Conversation
The test is still failing, even after adding an additional arg seperator I'm not able to debug and stuck here, any help or insights would be instrumental. cc : @thelovekesh @westonruter |
I see this https://github.com/WordPress/performance/actions/runs/11825633049/job/32949852740?pr=1653#step:12:49 which seems to be the problem:
|
Yes, there's no coverage file to upload and hence the test is failing, however the WorkFlow before uploading is running (where xml file is generated ) and the hash is also same I verified. cc : @westonruter |
I believe @thelovekesh has in mind what is wrong there. |
Welcome to Codecov 🎉Once you merge this PR into your default branch, you're all set! Codecov will compare coverage reports and display results in all future pull requests. Thanks for integrating Codecov - We've got you covered ☂️ |
Issue with Codecov upload report job :Currently Creating report in codecov is failing :
Latest Commit : https://github.com/WordPress/performance/actions/runs/12145298761/job/33866607688?pr=1653 However it was running fine in previous commits :
Error says token is required, but previously it was working, any idea why it might be the case here ? cc : @thelovekesh @westonruter |
The following accounts have interacted with this PR and/or linked issues. I will continue to update these lists as activity occurs. You can also manually ask me to refresh this list by adding the Unlinked AccountsThe following contributors have not linked their GitHub and WordPress.org accounts: @[email protected]. Contributors, please read how to link your accounts to ensure your work is properly credited in WordPress releases. If you're merging code through a pull request on GitHub, copy and paste the following into the bottom of the merge commit message.
To understand the WordPress project's expectations around crediting contributors, please review the Contributor Attribution page in the Core Handbook. |
I re-ran the Props Bot job that had failed due to |
I'll fix the platform ^7.2 issue and indentation issue soon, then we it'll be completed. 😄 |
run: npm run wp-env start | ||
run: | | ||
if [ "${{ matrix.coverage }}" == "true" ]; then | ||
npm run wp-env start -- --xdebug=develop,coverage |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is develop
a value for --xdebug
? I only see profile
, trace
, and debug
listed: https://developer.wordpress.org/block-editor/reference-guides/packages/packages-env/#using-xdebug
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes develop
is also a value for --xdebug
along with coverage
as mentioned here : https://xdebug.org/docs/code_coverage#mode
But we no longer need develop
so removing it.
cc : @westonruter
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks great! I'll defer to @felixarntz or @swissspidy to give final approval and merge.
When running tests locally in wp-env I'm now seeing this warning:
I guess this is because it is running PHPUnit 8.5.39 which is a version prior to this element being introduced. |
Note: I noticed that code coverage was being reported for test files, so I've excluded them in ca0ca13. |
Summary
This PR fixes the currently broken automated codecov coverage in github workflow.
Fixes #1284
Problem Reference - #1652 (comment)
Additional Technical Details Required
As mentioned here - #1586 (comment)
Currently the xml file name is being generated like
coverage-multisite-${{ github.sha }}.xml
, so if it's getting overwritten for each plugin, what different identifier can we use here so that it's unique for each plugin ?cc : @thelovekesh @westonruter