Skip to content

Conversation

ReillyBrogan
Copy link
Contributor

Dumb terminals are incapable of handling color, so this test would fail when ran in such an environment. We encountered this on the Solus build infrastructure which uses such a headless terminal.

Copy link
Member

@The-Compiler The-Compiler left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't think the test needs to be skipped if NO_COLOR is set, as monkeypatch in the test already takes care of that.

In the same vein, couldn't the test just set TERM to a known value instead of skipping the test, to make it work no matter what the "outside" TERM is?

Dumb terminals are incapable of handling color, so this test would fail
when ran in such an environment.
@psf-chronographer psf-chronographer bot added the bot:chronographer:provided (automation) changelog entry is part of PR label Oct 7, 2025
@bluetech
Copy link
Member

bluetech commented Oct 7, 2025

I applied @The-Compiler suggestion and confirmed that it works. Will merge once CI passes, thanks!

@bluetech bluetech enabled auto-merge October 7, 2025 08:17
@bluetech bluetech disabled auto-merge October 7, 2025 08:38
@bluetech bluetech merged commit 2c0acf1 into pytest-dev:main Oct 7, 2025
33 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

bot:chronographer:provided (automation) changelog entry is part of PR

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants