Skip to content

workflows: workaround Go 1.22 coverage problem #3339

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 1 commit into from
Mar 6, 2024

Conversation

roman-khimov
Copy link
Member

See golang/go#65653, the fix can be postponed up to Go 1.23 and we need green.

See golang/go#65653, the fix can be postponed up
to Go 1.23 and we need green.

Signed-off-by: Roman Khimov <[email protected]>
@roman-khimov roman-khimov added go Go language related test Unit tests labels Mar 6, 2024
Copy link

codecov bot commented Mar 6, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 84.73%. Comparing base (8d67f17) to head (d31b01d).
Report is 18 commits behind head on master.

Additional details and impacted files
@@            Coverage Diff             @@
##           master    #3339      +/-   ##
==========================================
- Coverage   84.87%   84.73%   -0.14%     
==========================================
  Files         328      331       +3     
  Lines       44835    44932      +97     
==========================================
+ Hits        38052    38073      +21     
- Misses       5270     5342      +72     
- Partials     1513     1517       +4     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

@AnnaShaleva AnnaShaleva added this to the v0.106.0 milestone Mar 6, 2024
@AnnaShaleva AnnaShaleva merged commit bdcc036 into master Mar 6, 2024
@AnnaShaleva AnnaShaleva deleted the workaround-coverage branch March 6, 2024 07:15
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
go Go language related test Unit tests
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants