Skip to content

Sync Docs branch with master - #2657

Open
anandhu-eng wants to merge 249 commits into
masterfrom
docs
Open

Sync Docs branch with master#2657
anandhu-eng wants to merge 249 commits into
masterfrom
docs

Conversation

@anandhu-eng

Copy link
Copy Markdown
Contributor

No description provided.

github-actions and others added 26 commits July 1, 2026 15:12
Adds docs/system-info/index.md covering the get-mlperf-multi-node-system-info
script for MLPerf Inference submissions: installation, quick start, config file
usage, serving framework detection, sample output, and a verified field
reference table aligned with SYSTEM_DESC_REQUIRED_FIELDS.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Clarifies that power and network mode fields are scoped for future
rounds and must be filled in manually before submission.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Adds a section covering the new _redfish and _inference_optional_nameplate
variations of get-mlperf-multi-node-system-info: the skeleton template
written when used alone, and real PSU data populated from a live Redfish
BMC when stacked with _redfish, including the Redfish-to-nameplate field
mapping and required CLI parameters.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Take master's versions of the three files that conflict when merging
docs into master:

  - e2e-rag/db_manifest.py
  - e2e-rag/datasetup_accuracy_eval.py
  - e2e-rag/reference_SUT_datasetup.py

The conflicts came from master's functional rewrites (#2645, #2625)
landing on top of the automated "Format Codebase" reflow of the older
code on docs. Docs never made a manual edit to these files, so master's
content is authoritative and nothing is lost.

The files are left byte-identical to master rather than reformatted:
autopep8 on the docs side rewrites the same line ranges master did,
which reintroduces the conflicts. Formatting can follow once both
branches agree on content.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
This reverts commit 7c17261 for e2e-rag/db_manifest.py.

The format.yml workflow reformatted db_manifest.py right after 765c476
made it byte-identical to master, which reintroduced the merge conflict
against master: autopep8 on the docs side rewrites the same line ranges
master's functional changes did.

Now that format.yml is removed from this branch (297a81d), the file can
stay byte-identical to master and docs merges into master cleanly.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
The docs branch carried autopep8 reformatting of e2e-rag Python files
that master never had, which showed up as pure formatting noise in the
docs -> master PR diff.

Reset these files to master's exact bytes. Verified at the token level
(ignoring whitespace and comments) that none of them contains any
docs-authored code: every difference was either autopep8 churn from the
now-removed format.yml workflow, or docs lagging master.

The autopep8 artifacts included reflowed call sites, trailing whitespace
stripped inside docstrings, reordered imports, and one long comment split
in a way that injected a stray '#'.

main.py is deliberately left alone: it carries docs-only commits.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Copy the entire e2e-rag directory from master so the docs branch carries
no divergence there at all. The remaining files were docs lagging master:
shell scripts, user.conf, .gitignore, README.md and the scripts/ helpers.

e2e-rag on docs is now byte-identical to master.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
@anandhu-eng
anandhu-eng requested review from a team as code owners August 26, 2026 17:19
@github-actions

Copy link
Copy Markdown
Contributor

MLCommons CLA bot All contributors have signed the MLCommons CLA ✍️ ✅

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