Skip to content

ci: fix renderer_regression_check on Windows CRLF manifest checkout#137

Merged
cursor[bot] merged 2 commits intomainfrom
cursor/renderer-regression-crlf-manifest-7dab
Apr 22, 2026
Merged

ci: fix renderer_regression_check on Windows CRLF manifest checkout#137
cursor[bot] merged 2 commits intomainfrom
cursor/renderer-regression-crlf-manifest-7dab

Conversation

@timfox
Copy link
Copy Markdown
Owner

@timfox timfox commented Apr 22, 2026

Problem

On Windows GitHub Actions runners, REGRESSION_REPO_MANIFEST.txt is often checked out with CRLF line endings. Each manifest path retained a trailing \r, so [ -f "$PROJECT_ROOT/$line" ] failed for every entry (~58 failures) even though the files exist.

Fix

  • scripts/renderer_regression_check.sh: strip trailing \r from each line when reading the repo manifest and when reading OPTIONAL_GAME_ASSETS.txt under GAME_BASE.

Docs

  • docs/RENDERER_CONFIDENCE.md: note CRLF-safe manifest parsing in the Tier A table.

Validation (Linux)

  • ./scripts/renderer_regression_check.sh
  • ./scripts/compile_engine.sh vulkan + opengl
  • ./scripts/smoke_test.sh
  • ctest -R 'smoke_test|renderer_regression'
  • ./scripts/validate_ci_build.sh
Open in Web Open in Cursor 

cursoragent and others added 2 commits April 22, 2026 00:27
Windows git checkouts use CRLF for REGRESSION_REPO_MANIFEST.txt; paths
kept a trailing \r so -f tests failed (58 manifest misses). Strip \r
from each line before the existence check and GAME_BASE asset paths.

Co-authored-by: Tim Fox <timfox@outlook.com>
@cursor cursor Bot marked this pull request as ready for review April 22, 2026 00:29
@cursor cursor Bot merged commit 8d6297b into main Apr 22, 2026
27 checks passed
@cursor cursor Bot deleted the cursor/renderer-regression-crlf-manifest-7dab branch April 22, 2026 00:29
Copy link
Copy Markdown

@cursor cursor Bot left a comment

Choose a reason for hiding this comment

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

Security review complete for this PR.

I found no new medium/high/critical vulnerabilities introduced by this change.

What I validated:

  • The new line="${line%$'\r'}" normalization in scripts/renderer_regression_check.sh only strips trailing carriage returns from manifest/asset-list lines.
  • No new attacker-controlled input reaches execution sinks (eval, command substitution, process spawning, file writes, network calls, or privilege boundaries) as part of this change.
  • The behavior change is limited to path-string normalization for existing file-presence checks and does not expand permissions or trust boundaries.

No inline security findings to report.

Open in Web View Automation 

Sent by Cursor Automation: Find vulnerabilities

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