Skip to content

Fix tests using assert_raise_with_message on US-ASCII systems #14251

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
Aug 16, 2025

Conversation

peterzhu2118
Copy link
Member

On systems where the Encoding.default_internal defaults to US-ASCII instead of UTF-8, some tests using assert_raise_with_message can fail since it no longer changes Encoding.default_internal in 79f5202.

This tests explicitly uses EnvUtil.with_default_internal on systems where these tests fail.

This comment has been minimized.

On systems where the Encoding.default_internal defaults to US-ASCII instead
of UTF-8, some tests using assert_raise_with_message can fail since it no
longer changes Encoding.default_internal in 79f5202.

This tests explicitly uses EnvUtil.with_default_internal on systems where
these tests fail.
@peterzhu2118 peterzhu2118 force-pushed the default-internal-us-ascii branch from 3c10b9e to ed38317 Compare August 16, 2025 01:42
@peterzhu2118 peterzhu2118 enabled auto-merge (rebase) August 16, 2025 01:43
@peterzhu2118 peterzhu2118 merged commit 87c4ebd into ruby:master Aug 16, 2025
85 checks passed
@peterzhu2118 peterzhu2118 deleted the default-internal-us-ascii branch August 16, 2025 03:20
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.

2 participants