Skip to content

Fix LegacyKeyValueFormat report from docker build: pr#153529

Merged
rust-bors[bot] merged 1 commit intorust-lang:mainfrom
homersimpsons:chore/fix-LegacyKeyValueFormat-pr
Mar 12, 2026
Merged

Fix LegacyKeyValueFormat report from docker build: pr#153529
rust-bors[bot] merged 1 commit intorust-lang:mainfrom
homersimpsons:chore/fix-LegacyKeyValueFormat-pr

Conversation

@homersimpsons
Copy link
Contributor

Part of #152305

r? @marcoieni

@rustbot rustbot added A-CI Area: Our Github Actions CI A-testsuite Area: The testsuite used to check the correctness of rustc S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. T-infra Relevant to the infrastructure team, which will review and decide on the PR/issue. labels Mar 7, 2026
Comment on lines +42 to 45
ENV SCRIPT=" \
# Check some tools that aren't included in `x check` by default, to
# ensure that maintainers can still do check builds locally.
python3 ../x.py check \
Copy link
Contributor Author

Choose a reason for hiding this comment

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

@marcoieni How would you like to handle this? (1 or 4 or other solution?)

Original outputs:

ENV SCRIPT_SOURCE \
  # Check some tools that aren't included in `x check` by default, to
  # ensure that maintainers can still do check builds locally.
  python3 ../x.py check
SCRIPT_SOURCE=python3 ../x.py check
  1. This outputs spaces:
ENV SCRIPT=" \
  # Check some tools that aren't included in `x check` by default, to
  # ensure that maintainers can still do check builds locally.
  python3 ../x.py check"
SCRIPT_TARGET=   python3 ../x.py check
  1. This does not compile:
ENV SCRIPT_TARGET="#Check some tools that aren't included in `x check` by default, to
  # ensure that maintainers can still do check builds locally.
  python3 ../x.py check"
Dockerfile:9
--------------------
   7 |     ENV SCRIPT_TARGET="#Check some tools that aren't included in `x check` by default, to
   8 |       # ensure that maintainers can still do check builds locally.
   9 | >>>   python3 ../x.py check"
  10 |
  11 |     CMD ["printenv"]
--------------------
ERROR: failed to build: failed to solve: dockerfile parse error on line 9: unknown instruction: python3
  1. This does not work as it compiles with the comment inline:
ENV SCRIPT_TARGET="#Check some tools that aren't included in `x check` by default, to \
  # ensure that maintainers can still do check builds locally.
  python3 ../x.py check"
SCRIPT_TARGET=#Check some tools that aren't included in `x check` by default, to   python3 ../x.py check
  1. This works, moving the comment:
# Check some tools that aren't included in `x check` by default, to
# ensure that maintainers can still do check builds locally.
ENV SCRIPT_TARGET="python3 ../x.py check"
SCRIPT_TARGET=python3 ../x.py check

Copy link
Member

Choose a reason for hiding this comment

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

your solution looks good!

@marcoieni
Copy link
Member

@bors r+ rollup=always

@rust-bors
Copy link
Contributor

rust-bors bot commented Mar 12, 2026

📌 Commit fcfd96e has been approved by marcoieni

It is now in the queue for this repository.

@rust-bors rust-bors bot added S-waiting-on-bors Status: Waiting on bors to run and complete tests. Bors will change the label on completion. and removed S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. labels Mar 12, 2026
Zalathar added a commit to Zalathar/rust that referenced this pull request Mar 12, 2026
…alueFormat-pr, r=marcoieni

Fix LegacyKeyValueFormat report from docker build: pr

Part of rust-lang#152305

r? @marcoieni
rust-bors bot pushed a commit that referenced this pull request Mar 12, 2026
Rollup of 11 pull requests

Successful merges:

 - #153726 (Add optional CI job to build the compiler with the parallel frontend)
 - #153763 (Don't add empty target features for target-cpu=native on macOS)
 - #153432 (Fix some comments about dataflow analysis.)
 - #153529 (Fix LegacyKeyValueFormat report from docker build: pr)
 - #153694 (fix(query): Pass Query Key to `value_from_cycle_error`)
 - #153708 (de-non_const `Iterator` trait methods)
 - #153717 (unused_macro_rules switched used and unused comments)
 - #153736 (add test that an incomplete feature emits a warning)
 - #153748 (editorconfig: css uses tabs)
 - #153750 (rustc-dev-guide subtree update)
 - #153762 (actually make the is-fn test test what it says it tests)
Zalathar added a commit to Zalathar/rust that referenced this pull request Mar 12, 2026
…alueFormat-pr, r=marcoieni

Fix LegacyKeyValueFormat report from docker build: pr

Part of rust-lang#152305

r? @marcoieni
rust-bors bot pushed a commit that referenced this pull request Mar 12, 2026
…uwer

Rollup of 10 pull requests

Successful merges:

 - #153726 (Add optional CI job to build the compiler with the parallel frontend)
 - #153763 (Don't add empty target features for target-cpu=native on macOS)
 - #153432 (Fix some comments about dataflow analysis.)
 - #153529 (Fix LegacyKeyValueFormat report from docker build: pr)
 - #153694 (fix(query): Pass Query Key to `value_from_cycle_error`)
 - #153717 (unused_macro_rules switched used and unused comments)
 - #153736 (add test that an incomplete feature emits a warning)
 - #153748 (editorconfig: css uses tabs)
 - #153750 (rustc-dev-guide subtree update)
 - #153762 (actually make the is-fn test test what it says it tests)
@rust-bors rust-bors bot merged commit 8aea29b into rust-lang:main Mar 12, 2026
11 checks passed
@rustbot rustbot added this to the 1.96.0 milestone Mar 12, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

A-CI Area: Our Github Actions CI A-testsuite Area: The testsuite used to check the correctness of rustc S-waiting-on-bors Status: Waiting on bors to run and complete tests. Bors will change the label on completion. T-infra Relevant to the infrastructure team, which will review and decide on the PR/issue.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants