Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Conversation

@Spacetown
Copy link
Member

Update the logging to use a coloured output if running in a TTY or the user forced it by setting --force-color in the CLI or by defining the environment variable FORCE_COLOR as described in http://force-color.org.
In the pipeline the color is forced (introduced for nox by #698). If a test is failing we get now a coloured output of gcovr execution.

@Spacetown Spacetown added this to the Upcoming release milestone Feb 16, 2024
@codecov
Copy link

codecov bot commented Feb 16, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Comparison is base (52c88f0) 95.30% compared to head (ba2db84) 95.33%.

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #887      +/-   ##
==========================================
+ Coverage   95.30%   95.33%   +0.03%     
==========================================
  Files          54       54              
  Lines        4534     4544      +10     
  Branches      893      893              
==========================================
+ Hits         4321     4332      +11     
  Misses        130      130              
+ Partials       83       82       -1     

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

@Spacetown Spacetown marked this pull request as ready for review February 16, 2024 21:07
@Spacetown Spacetown merged commit 023dec1 into gcovr:main Feb 16, 2024
@Spacetown Spacetown deleted the improve_logging branch February 16, 2024 21:09
@Spacetown Spacetown removed this from the Upcoming release milestone Feb 25, 2024
D-Walther pushed a commit to D-Walther/gcovr that referenced this pull request Jun 16, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant