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

Fix noxfile coverage arguments #1033

Merged
merged 2 commits into from
May 8, 2024

Conversation

thom-at-redhat
Copy link
Contributor

No description provided.

Copy link

codecov bot commented May 8, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 42.38%. Comparing base (9b58ca7) to head (4298344).
Report is 78 commits behind head on devel.

@@            Coverage Diff             @@
##            devel    #1033      +/-   ##
==========================================
+ Coverage   41.82%   42.38%   +0.55%     
==========================================
  Files          42       45       +3     
  Lines        6640     7220     +580     
==========================================
+ Hits         2777     3060     +283     
- Misses       3646     3941     +295     
- Partials      217      219       +2     

see 6 files with indirect coverage changes

Components Coverage Δ
Go 41.77% <ø> (-0.05%) ⬇️
Receptorctl 49.31% <ø> (∅)

@thom-at-redhat thom-at-redhat added the type:bug Something isn't working label May 8, 2024
Copy link

sonarcloud bot commented May 8, 2024

Quality Gate Passed Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
No data about Coverage
0.0% Duplication on New Code

See analysis details on SonarCloud

@thom-at-redhat thom-at-redhat merged commit cb34c36 into ansible:devel May 8, 2024
23 checks passed
@thom-at-redhat thom-at-redhat deleted the fix_noxfile_coverage branch May 8, 2024 20:35
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type:bug Something isn't working
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants