Skip to content

Support TASKING option files and improve response-file caching - #2826

Open
Joldiges wants to merge 3 commits into
mozilla:mainfrom
Joldiges:upstream/tasking-option-files
Open

Support TASKING option files and improve response-file caching#2826
Joldiges wants to merge 3 commits into
mozilla:mainfrom
Joldiges:upstream/tasking-option-files

Conversation

@Joldiges

Copy link
Copy Markdown

TASKING invocations generated with -f or --option-file were rejected as non-cacheable because their contained compiler arguments were not expanded before parsing.

Expand TASKING option files before argument classification, including joined, separated, abbreviated, quoted, continued, and nested forms. Malformed, unreadable, or excessively nested files fall back safely instead of producing an incomplete cache key. Add focused coverage for the supported forms and failure cases.

GitHub copilot was used for the debugging and resolution of this issue.

Expand TASKING -f and --option-file arguments before parsing so generated response-file builds can be cached safely.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Copilot AI lite review requested due to automatic review settings August 27, 2026 09:37

Copilot AI left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Pull request overview

This PR makes TASKING VX invocations cacheable when they use -f / --option-file by expanding option-file contents into the argument stream before classification/parsing, so the expanded arguments are included in the cache key.

Changes:

  • Expand -f / --option-file (including abbreviated, concatenated, =-joined, comma-separated, line-continued, quoted, and nested forms) prior to ArgsIter parsing.
  • Update TASKING argument dispositions to allow =-joined options to be parsed/normalized consistently (CanBeSeparated(b'=')).
  • Add focused unit tests covering successful expansion and safe fallback cases (missing file, unterminated quotes, nesting limit, and “option-file-like” values that must not expand).

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

Comment thread src/compiler/tasking_vx.rs
Joldiges and others added 2 commits August 27, 2026 05:48
Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com>
Do not let unknown options containing an inline equals value suppress expansion of a following option-file argument. Cover both populated and empty inline values.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
@Joldiges
Joldiges marked this pull request as draft August 27, 2026 20:59
@Joldiges
Joldiges marked this pull request as ready for review August 28, 2026 15:24
@codecov-commenter

codecov-commenter commented Aug 28, 2026

Copy link
Copy Markdown

Codecov Report

❌ Patch coverage is 89.47368% with 40 lines in your changes missing coverage. Please review.
✅ Project coverage is 70.23%. Comparing base (8ab3926) to head (f641db5).
⚠️ Report is 1 commits behind head on main.

Files with missing lines Patch % Lines
src/compiler/tasking_vx.rs 89.47% 40 Missing ⚠️
Additional details and impacted files
@@            Coverage Diff             @@
##             main    #2826      +/-   ##
==========================================
- Coverage   73.71%   70.23%   -3.48%     
==========================================
  Files          72       72              
  Lines       37932    38266     +334     
==========================================
- Hits        27963    26878    -1085     
- Misses       9969    11388    +1419     

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

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.

4 participants