Skip to content

test(ios-simulator): pin utf-8 on 6 subprocess calls - #27261

Merged
javenciu merged 1 commit into
mainfrom
test/subprocess-encoding-ios-simulator-preview-skill
Nov 1, 2026
Merged

javenciu merged 1 commit into
mainfrom
test/subprocess-encoding-ios-simulator-preview-skill

Conversation

@javenciu

@javenciu javenciu commented Nov 1, 2026

Copy link
Copy Markdown
Contributor

Problem / Motivation

Goal: A text-mode subprocess call in 1 file decodes its child's output as UTF-8 on every platform instead of the locale's code page.

The subprocess-encoding gate counts, per file, the sites the repo still tolerates. This PR retires: 6 test/test_ios_simulator_preview_skill.py.

Why it matters

Without an explicit encoding, subprocess.run(..., text=True) decodes with the locale code page, which on Windows is not UTF-8: non-ASCII output becomes mojibake or raises UnicodeDecodeError (#5249). The repo lists every such call per file in .github/subprocess-encoding-baseline.txt and the gate lets each count only shrink.

Not a goal

  • Calls in files not listed here (each is its own one-mechanism PR).
  • Changing what any child process does or how its output is used.
  • Any refactor or reformatting of untouched lines.

What changed (motivation → approach → change)

Each call below now passes encoding="utf-8" beside its text=True, and the file's baseline line is removed. A call whose child is Python (sys.executable) also starts it with -X utf8, so the child writes UTF-8 on every platform and the pinned decoder matches it; without UTF-8 mode, a Python child on Windows writes its console code page.

  • test/test_ios_simulator_preview_skill.py:216: the run(...) call in test_timeout_produces_parseable_json_at_runtime
  • test/test_ios_simulator_preview_skill.py:277: the run(...) call in test_stale_pidfile_triggers_no_vendor_cleanup_at_runtime
  • test/test_ios_simulator_preview_skill.py:328: the run(...) call in test_wedged_simctl_reports_json_error_at_runtime
  • test/test_ios_simulator_preview_skill.py:370: the run(...) call in test_relative_data_home_errors_at_runtime
  • test/test_ios_simulator_preview_skill.py:388: the run(...) call in test_tilde_data_home_is_expanded_at_runtime
  • test/test_ios_simulator_preview_skill.py:432: the run(...) call in test_symlinked_log_is_not_written_through_at_runtime
  • .github/subprocess-encoding-baseline.txt: removed 6 test/test_ios_simulator_preview_skill.py.

Backwards compatibility

Compatible: test-only change
Removes nothing: a baseline entry is a tolerance the gate stops needing, not a capability.

Tests

  • Red: with the file put back to main and the baseline line still deleted, RATCHET_SCOPE_WHOLE_TREE=1 python3 scripts/check_subprocess_encoding.py exits 1: ::error file=test/test_ios_simulator_preview_skill.py::text-mode subprocess call without encoding= (decodes with the ....
  • Green: with the edit, python3 scripts/check_subprocess_encoding.py --test && python3 scripts/check_subprocess_encoding.py exit 0.
  • test/test_ios_simulator_preview_skill.py: 29 passed with the edit
  • flake8 clean on the touched file; the repo's baselined black gate passes.

Manual verification

N/A: the subprocess-encoding gate checks the changed call directly.

Screenshots / video

Why no screenshot: nothing renders; this change touches test code and a CI baseline only.

No issue exists; burn-down of the subprocess-encoding gate baseline (precedents #20146, #20142, #20147).

Pin UTF-8 on the text-mode subprocess call(s) in test/test_ios_simulator_preview_skill.py and drop the file's row
from .github/subprocess-encoding-baseline.txt, so the subprocess-encoding gate stops tolerating it.
@javenciu
javenciu requested review from a team and KiroCrewCaptain as code owners November 1, 2026 18:29
@javenciu
javenciu requested a review from buluoray November 1, 2026 18:29
@github-actions github-actions Bot added the readiness: checking Automated validation is still running label Nov 1, 2026
@github-actions

github-actions Bot commented Nov 1, 2026

Copy link
Copy Markdown
Contributor

First Principles Review (Opus 5.5) — ⏭️ skipped

Revision 182073e90bb4a0fffb186d3d146ea93faf7c3a1f ships no reviewable capability (docs, tests or generated files only), so there is nothing to inventory. Does not block merge.

@github-actions

github-actions Bot commented Nov 1, 2026

Copy link
Copy Markdown
Contributor

UX Review (Opus 5.5) — ⏭️ skipped

Revision 182073e90bb4a0fffb186d3d146ea93faf7c3a1f touches no user-facing surface (no changes under website/ or committed screenshots), so the UX review was skipped. Does not block merge.

@github-actions

github-actions Bot commented Nov 1, 2026

Copy link
Copy Markdown
Contributor

Design Review (Opus 5.5) — ✅ PASS

Design-level review of 182073e90bb4a0fffb186d3d146ea93faf7c3a1f — updated in place on each push. A BLOCK verdict blocks PR readiness; PASS does not.

Design-Verdict: PASS

Nothing to check. This is a test-only encoding pin that shrinks the baseline and follows the precedent burn-down PRs.

[DESIGN-REVIEWED] 182073e

Description read

[DESCRIPTION-READ] b79d934299873236dfd3e175576bf3422e47d8942937006cf2af638586b5f4d1

That sha256 names everything this verdict read: the PR description, plus the 1 evidence file(s) the workflow collected from it and handed this review. It covers that evidence because the media strip replaces every attachment URL with the same placeholder, so an edit swapping one attachment for another would leave the description's captured text identical while what this review judged changed. Recompute it with .github/scripts/pr-description-capture.sh over the same inputs; if it differs, the description or that evidence changed after this verdict was formed and any finding drawn from either is unproven.

@github-actions

github-actions Bot commented Nov 1, 2026

Copy link
Copy Markdown
Contributor

GPT 6.1 Review — ✅ no blocking findings

GPT 6.1 completed its review of 182073e90bb4a0fffb186d3d146ea93faf7c3a1f and found no blocking issues.

This comment is updated in place on each push.

Review details

No findings.
[GPT-REVIEWED] 182073e

False positive or not applicable? A repository writer can comment:
/ai-review override gpt 182073e90bb4a0fffb186d3d146ea93faf7c3a1f false-positive: <reason, 20 to 500 characters>

@github-actions

github-actions Bot commented Nov 1, 2026

Copy link
Copy Markdown
Contributor

Opus 5.5 Review — ✅ no blocking findings

Reviewed 182073e90bb4a0fffb186d3d146ea93faf7c3a1f — this comment is updated in place on each push.

Review details

No findings.

[OPUS-REVIEWED] 182073e

Verdict parsed from the review's SHA-scoped output markers for commit 182073e90bb4a0fffb186d3d146ea93faf7c3a1f.

False positive or not applicable? A repository writer can comment:
/ai-review override fable 182073e90bb4a0fffb186d3d146ea93faf7c3a1f false-positive: <reason, 20 to 500 characters>

@github-actions github-actions Bot added readiness: passed Eligible automated validation passed for the current revision and removed readiness: checking Automated validation is still running labels Nov 1, 2026
@javenciu
javenciu enabled auto-merge (squash) November 1, 2026 19:18

@KiroCrewCaptain KiroCrewCaptain left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

Tier 1 auto-approve: test (2 files). Criteria: no conflict, no requested changes, security path denylist clean, design-doc gate clean, security checklist all-NO, no reviewer-lane findings, readiness signal fresh for this head SHA, declared category matches the diff. Category: pins UTF-8 on six iOS simulator skill test subprocess calls and drops the file from the subprocess-encoding baseline.

@javenciu
javenciu merged commit 8cbfe5e into main Nov 1, 2026
95 checks passed
@javenciu
javenciu deleted the test/subprocess-encoding-ios-simulator-preview-skill branch November 1, 2026 20:33
@github-actions github-actions Bot removed the readiness: passed Eligible automated validation passed for the current revision label Nov 1, 2026
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