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

unset NO_COLOR env var when building. #738

Merged
merged 1 commit into from
Mar 14, 2022

Conversation

gugod
Copy link
Owner

@gugod gugod commented Mar 14, 2022

Setting NO_COLOR=1 would lead to test failures for a few modules in corelist.

This var changes the behaviour of Term::ANSIColor module in corelist
since version 5.01 and make it produce no colors code at all.

the "podlator" moduled included in perl dist contain tests that
verifies the existence of certain color codes and therefore would
break when NO_COLOR is set.

see also: #737

Fixes #737

Setting NO_COLOR=1 would lead to test failures for a few modules in corelist.

This var changes the behaviour of Term::ANSIColor module in corelist
since version 5.01 and make it produce no colors code at all.

the "podlator" moduled included in perl dist contain tests that
verifies the existence of certain color codes and therefore would
break when NO_COLOR is set.

see also: #737
@coveralls
Copy link

Coverage Status

Coverage remained the same at 77.436% when pulling 0fbeec4 on feature/unset-no-color-var-before-build into 4b06aa1 on develop.

@gugod gugod merged commit 8a83c3a into develop Mar 14, 2022
@gugod gugod deleted the feature/unset-no-color-var-before-build branch March 14, 2022 13:17
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

NO_COLOR env var lead to Test failures on macOS 11.6.4 (big sur) when installing perl-5.34.1
2 participants