You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug, including details regarding any error messages, version, and platform.
Google benchmark removed the long deprecated color_print cli flag in 1.6.1. This will cause the benchmarks to error when run if benchmark version >=1.6.1 is used. We bundle 1.7.1 since 12.0.0.
We set this flag unconditionally to false (for historic reasons I assume as this change is from 2017) here. I think we should not set the flag at all which will default to detecting if the env supports tty colors. If this causes cli issue we should set the correct flag and make it configurable.
Component(s)
C++
The text was updated successfully, but these errors were encountered:
### Rationale for this change
The deprecated flag causes errors on benchmark >= 1.6.1.
### Are there any user-facing changes?
No, benchmark defaults to an auto option to determine if colors are supported or not.
* Closes: #36076
Authored-by: Jacob Wujciak-Jens <jacob@wujciak.de>
Signed-off-by: Jacob Wujciak-Jens <jacob@wujciak.de>
Describe the bug, including details regarding any error messages, version, and platform.
Google benchmark removed the long deprecated
color_print
cli flag in 1.6.1. This will cause the benchmarks to error when run if benchmark version >=1.6.1 is used. We bundle 1.7.1 since 12.0.0.We set this flag unconditionally to false (for historic reasons I assume as this change is from 2017) here. I think we should not set the flag at all which will default to detecting if the env supports tty colors. If this causes cli issue we should set the correct flag and make it configurable.
Component(s)
C++
The text was updated successfully, but these errors were encountered: