Skip to content

ci: remove the W7900 lane from e2e-selfhosted - #1066

Merged
tomastola merged 3 commits into
mainfrom
ci/retire-w7900-push-lane
Nov 13, 2026
Merged

tomastola merged 3 commits into
mainfrom
ci/retire-w7900-push-lane

Conversation

@tomastola

@tomastola tomastola commented Nov 12, 2026 •

Copy link
Copy Markdown
Collaborator

What

Removes the e2e-gpu-w7900 lane from e2e-selfhosted.yml, so that together with #1063 (which removes the W7900 nightly job) no workflow targets the w7900 runner label. Follow-up to #1018, which already took the lane off pull_request and merge_group; it still ran on push, release/** and dispatch.

Changes

  • e2e-selfhosted.yml: delete the job, its w7900 dispatch choice, and its entries in e2e-report (needs and LANE_REPORTS); update the header comments.
  • xtask workflow_contract: drop the lane from the pinned event gates and the preflight lane counts (8 → 7).
  • xtask e2e_report: drop the -n-1/-n-2 W7900 artifact names (the lane was the only uploader).
  • Docs: docs/ci-hardware-testing.md, tests/e2e-cucumber/README.md and a doc comment.

Coverage

W7900 is covered only by the scheduled queue nightly's w7900-dual lane (advisory), not on push, release/** or dispatch. That lane has run: the 11-13 queue nightly (https://github.com/ROCm/rocm-cli/actions/runs/43351651832) got capacity at once and finished Done, exit 0.

Relationship to #1063

#1063 edits some of the same docs lines and the same preflight lane counts in workflow_contract.rs (8 → 4 there, 7 here; 3 once both land), so the second to merge needs a small rebase. The e2e-gpu-w7900-report artifact name and the descriptor rows are kept here because the nightly W7900 job still uploads them until #1063 merges; no workflow-file hunks overlap.

Testing

cargo test -p xtask (857 passed), cargo clippy --workspace --all-targets -- -D warnings, cargo fmt --check.

@github-actions

github-actions Bot commented Nov 12, 2026 •

Copy link
Copy Markdown
Contributor
Security scan found no critical or high findings on lines changed by this pull request

View the security scan run for complete reports.

“New” means the finding is located in a changed file on an added or modified line; it is not a base-versus-head findings delta.

The W7900 job targets a runner label nothing else uses, and it has not
run on pull_request or merge_group since the one-Linux-node change. Its
push, release and dispatch runs sat queued behind the single runner.
Remove the job, its dispatch choice, its report artifacts and the
consolidated-report entries, and update the workflow contract and docs.
W7900 hardware is covered by the queue.

Signed-off-by: Tomas Saaristola <tsaarist@amd.com>
@tomastola
tomastola force-pushed the ci/retire-w7900-push-lane branch from 1548ebd to f487d20 Compare November 13, 2026 10:45
@tomastola

Copy link
Copy Markdown
Collaborator Author

CI status on the earlier head (1548ebd):

  • clippy, "Windows build and test (debug)", windows-build-and-test (run 43224531032): this PR's own fault, a for loop over a single element in workflow_contract.rs (clippy::single_element_loop). Fixed in f487d20, which is also rebased onto current main; clippy -D warnings and cargo test -p xtask pass locally.
  • E2E tests (MI300X, current) (run 43224531139): not caused by this PR, which removes a W7900 job and edits xtask tests and docs, nothing the MI300X lane runs. But I can't say the failures are only the known set from the queue nightly on main (chat-06, serve-01, serve-02, serve-53, runtime-03, runtime-04). The run reported 12 failed scenarios: 4 expected failures (xfail, which likely cover chat-06, serve-01, serve-02, serve-53) and 8 unexpected ones: bench-06, chat-07, serve-05, serve-50, serve-51, serve-52, serve-54 and a runtime lifecycle activate/restart scenario. Apart from that last one, which I did not map to runtime-03/04, those are not on the nightly list. The lane reruns on the new head.

@tomastola
tomastola marked this pull request as ready for review November 13, 2026 10:46
@tomastola
tomastola requested a review from a team as a code owner November 13, 2026 10:46
@tomastola
tomastola requested a review from juhovainio November 13, 2026 10:46

@juhovainio juhovainio 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.

Thanks for the cleanup. The workflow change itself looks fine to me and matches the PR description; I found nothing blocking in the YAML. I'm requesting changes only because the docs overstate the result.

  • The header comment in e2e-selfhosted.yml and docs/ci-hardware-testing.md say W7900 is "covered by the queue". The queue docs and queue-run.yml don't mention W7900, and the description itself says the w7900-dual lane hasn't run yet. Until it does, W7900 has no coverage on push, release/** or dispatch. Please reword both (inline comments below).
  • docs/testing.md (around line 3069) still describes W7900 as a PR lane. It's outside this diff so I can't comment inline, but it should be updated here too.

Leftovers (the e2e-gpu-w7900-report artifact name, descriptor rows, release_readiness.rs, e2e_report.rs) are deferred to #1063 as the description says; whichever of the two merges second will need a rebase.

CI: the two Security scan checks were red when I looked, with cancelled jobs beside their reruns, so possibly an artefact; worth a rerun. Several other jobs were still running.

Comment thread .github/workflows/e2e-selfhosted.yml Outdated
# Ubuntu and W7900 lanes keep their push / dispatch triggers and run nightly
# (nightly.yml); neither starts on pull_request or merge_group.
# Ubuntu lane keeps its push / dispatch triggers; it does not start on
# pull_request or merge_group. There is no W7900 lane: that hardware is covered

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.

"that hardware is covered by the queue" is stronger than what's true today: docs/nightly-on-the-queue.md and queue-run.yml don't mention W7900 at this head, and the PR description says the queue's w7900-dual lane hasn't run yet. Suggest wording that matches the description, e.g. "intended to be covered by the queue's w7900-dual lane once it has run".

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

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

Reworded in d5233a6: the header now says W7900 is covered only by the scheduled queue nightly's w7900-dual lane, not on push, release/** or dispatch. One fact changed since the description: the 11-13 queue nightly (https://github.com/ROCm/rocm-cli/actions/runs/43351651832) did run w7900-dual: it got capacity at once and finished Done, exit 0 (advisory lane, 13 files collected), so I no longer say it has not run.

Comment thread docs/ci-hardware-testing.md Outdated
DevLab Dispatch pool labels, `e2e-gpu-nightly-w7900`).
Ubuntu lane (`e2e-gpu-strix-ubuntu`) no longer starts on `pull_request` or in
the merge queue; it keeps its `push`/dispatch triggers. There is no W7900 lane
in `e2e-selfhosted.yml` any more: that hardware is covered by the queue (below).

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.

Same claim here: "covered by the queue (below)", but nothing below names W7900. Please reword to say W7900 has no coverage until the queue lane runs, so the doc doesn't promise coverage that doesn't exist yet.

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

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

Reworded in d5233a6: W7900 is covered only by the scheduled queue nightly's w7900-dual lane (advisory), not on push, release/** or dispatch, and the first run is cited (https://github.com/ROCm/rocm-cli/actions/runs/43351651832, Done, exit 0). docs/nightly-on-the-queue.md omitted the lane, so it now names w7900-dual and says it is the only scheduled W7900 coverage.

@nowycondro nowycondro 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.

Review — needs work

Full review of the whole change (base 4221d665…head f487d208). No ticket named in the description beyond cross-references to sibling/predecessor PRs (#1018, #1063); this change matches its stated scope of removing the W7900 lane from e2e-selfhosted.yml only.

Blocking

  • Doc paragraph still attributes a W7900 artifact name to a workflow that no longer produces it — docs/ci-hardware-testing.md:324-332
    The "lane artifacts are named canonically (...)" paragraph lists e2e-gpu-w7900-report among names produced "in ci.yml and e2e-selfhosted.yml". Verified at the base commit that this was true (the now-deleted job uploaded exactly that name); after this PR removes the whole e2e-gpu-w7900 job from e2e-selfhosted.yml, that literal artifact name is only reachable via nightly.yml's channel-matrix upload (e2e-gpu-w7900-release-report / -nightly-report, which the project's own artifact-naming test strips to this base name for comparison). The sentence needs to either drop this entry or correctly attribute it to nightly.yml. The paragraph's next sentence also explains why rad3/mi350p have no -n-1/-n-2 entries (nightly-only lanes) but doesn't mention that e2e-gpu-w7900-report is now in the exact same position, despite losing its own -n-1/-n-2 entries in this very diff.
    Confidence 85 · mechanical · Fix: reword to scope e2e-gpu-w7900-report to nightly.yml (or explain it's kept only for the cross-workflow comparison test), and fold it into the nightly-only explanation alongside rad3/mi350p.

Non-blocking

  • Narrative comments in the contract-test file still say "eight" after the assertions were updated to seven — xtask/src/workflow_contract.rs:2836-2837, 2888, 2897-2898, 2920, 2936, 2969, 2981, 4315
    The assert_eq! counts in every_native_linux_preflight_delegates_to_the_shared_script and its sibling tests were correctly bumped from 8 to 7, but several nearby prose comments explaining the same invariant ("the eight native Linux preflights are now one script plus a floor", "the eight are one gate in name only", etc.) were left saying "eight". These counts were accurate pre-PR and simply weren't touched here.
    Confidence 80 · mechanical · Fix: update the remaining "eight" mentions to "seven" for consistency with the assertions right next to them.

Decisions for the author

  • Stale "mirrors the e2e-gpu-w7900 lane... in e2e-selfhosted.yml" comment in nightly.yml — answered-by-intent
    The still-existing e2e-gpu-nightly-w7900 job's header comment says it "Mirrors the e2e-gpu-w7900 lane (which no longer runs on pull_request) in e2e-selfhosted.yml" and "Keep the two in step" — both go stale the moment this PR merges, since that lane is now gone entirely rather than merely restricted. The PR description states the linked follow-up "removes the W7900 nightly job" outright, which would delete this comment along with it. Would otherwise be a blocking doc-accuracy finding; worth confirming that follow-up lands soon so the staleness window stays short.
  • Whether the static nightly W7900 job becomes redundant with the shared GPU queue — tradeoff
    The new comment in e2e-selfhosted.yml frames the hardware as now "covered by the queue," while nightly.yml still runs its own dedicated, differently-triggered e2e-gpu-nightly-w7900 job. If the queue's lane is meant to be the long-term coverage, worth confirming whether the static nightly job is also being retired, or intentionally kept running in parallel for a while.

Positive signals

  • Unusually thorough propagation for a lane removal: the workflow_dispatch choice list, the consolidated-report needs list and LANE_REPORTS map, the pinned event-gate test, and the preflight-lane count were all updated together in one pass, and the one genuinely cross-cutting case was handled correctly (the CANONICAL_REPORT_ARTIFACTS list kept the bare artifact name specifically because nightly.yml still produces it).

Deployment notes

None.

What this covered

Read the full diff (6 files) completely, plus the current full text of .github/workflows/e2e-selfhosted.yml, .github/workflows/nightly.yml, docs/ci-hardware-testing.md, docs/nightly-on-the-queue.md, xtask/src/workflow_contract.rs and xtask/src/e2e_report.rs at the head commit, and a repository-wide search for remaining w7900 references to check blast radius beyond the touched files. Two independent passes covered (a) the workflow file plus its contract-test, and (b) the docs/README/report-artifact files, and converged on the same doc findings reported above. CI on the PR is green (an earlier security-scan run failure was superseded by a later successful run on the same commit). Not reconciled against any prior review or PR discussion thread.

e2e-selfhosted.yml has no W7900 lane any more, so e2e-gpu-w7900-report
is uploaded only by nightly.yml, like the rad3 and mi350p reports. Say
so next to them, and bring the lane-count comments in line with the
seven lanes the assertions now pin.

Signed-off-by: Tomas Saaristola <tsaarist@amd.com>
@tomastola

Copy link
Copy Markdown
Collaborator Author

Thanks. Taken in 1c99c06:

  • Blocking, docs/ci-hardware-testing.md artifact list: confirmed. e2e-gpu-w7900-report is now uploaded only by nightly.yml (as e2e-gpu-w7900-<channel>-report), so listing it under "in ci.yml and e2e-selfhosted.yml" was wrong. The sentence next to rad3 and mi350p now covers all three: they are uploaded only by nightly.yml and have no -n-1/-n-2 entries. The name stays in the list because hardware_testing_docs_cover_all_self_hosted_platforms requires every uploaded artifact there.
  • Non-blocking, "eight" in workflow_contract.rs comments: confirmed, the comments (around 2836-2981 and 4315) now say seven, matching the assertions.
  • Non-blocking, stale comment on e2e-gpu-nightly-w7900 in nightly.yml ("Mirrors the e2e-gpu-w7900 lane ... Keep the two in step"): confirmed stale, since the lane it mirrors is removed here. Not edited in this PR: ci: retire the self-hosted nightly lanes that never get a runner; keep the queue's GPUs in the wiki #1063 deletes that whole job, so editing it here would only conflict with that. If ci: retire the self-hosted nightly lanes that never get a runner; keep the queue's GPUs in the wiki #1063 does not land, it needs a one-line fix.

cargo test -p xtask (859 passed) and clippy with -D warnings pass locally.

@tomastola
tomastola requested a review from juhovainio November 13, 2026 11:28
The comment and docs claimed the queue covers W7900, which neither the
queue docs nor queue-run.yml said. Name the w7900-dual lane in the queue
doc, cite the 11-13 queue nightly where it ran and finished Done, and
state that W7900 has no coverage on push, release/** or dispatch. Fix
the testing guide, which still listed W7900 as a pull-request lane.

Signed-off-by: Tomas Saaristola <tsaarist@amd.com>
@tomastola

Copy link
Copy Markdown
Collaborator Author

Thanks @juhovainio. All three points are in d5233a6 (together with the earlier bot-review fixes in 1c99c06):

  1. "Covered by the queue" overstated: reworded in e2e-selfhosted.yml and docs/ci-hardware-testing.md to "covered only by the scheduled queue nightly's w7900-dual lane, not on push, release/** or dispatch". The queue doc omitted the lane, so docs/nightly-on-the-queue.md now names it (advisory). I checked the 11-13 queue nightly (https://github.com/ROCm/rocm-cli/actions/runs/43351651832): w7900-dual ran, phase Done, exit 0, 13 files collected, so the description's "has not run yet" is out of date too; I updated it. The run as a whole is red from other lanes.
  2. docs/testing.md ~3069: it said the W7900 lane runs on pull requests. It now says W7900 is on the queue nightly only, and that MI300X and the Strix Halo Windows and WSL2 lanes are the ones on pull requests.
  3. Security scan: I'll rerun the failed jobs if they are still red after this push.

cargo test -p xtask (859 passed) and clippy with -D warnings pass locally.

@juhovainio juhovainio 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.

Looks good to me. The deleted job, its needs entry, the LANE_REPORTS row and the dispatch option all come out together, and the workflow-contract counts (8 to 7, "all four lanes") match what's left. No action pins changed and nothing internal leaked into the diff. There's no user-visible CLI change, so no scenario is needed.

A few non-blocking things:

  • The docs state that the 11-13 queue nightly's w7900-dual lane "finished Done, exit 0". That run's overall conclusion is failure (exit code 1 in "Run and publish"), and I couldn't confirm the per-lane result. Please verify it or drop the run-specific claim, since it lands in durable docs (also repeated in nightly-on-the-queue.md and the PR body).
  • nightly.yml (around lines 674-676) still says it mirrors the e2e-gpu-w7900 lane in e2e-selfhosted.yml. I assume #1063 clears that; if it lands second or not at all, the comment goes stale.
  • The release-candidate gate loses its W7900 signal before tagging. The PR says so; just confirming that is intended.
  • Nit in the docs/testing.md hunk: "Of those" after the Lemonade lane list is slightly misleading, since MI300X is the vLLM lane.

CI: everything that had finished at the time of review passes; the affected-crates, Windows, mock E2E and coverage jobs were still running.

Ubuntu lane (`e2e-gpu-strix-ubuntu`) no longer starts on `pull_request` or in
the merge queue; it keeps its `push`/dispatch triggers. There is no W7900 lane
in `e2e-selfhosted.yml` any more: W7900 is covered only by the scheduled queue
nightly's `w7900-dual` lane (below; advisory), not on `push`, `release/**` or

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.

"(below; advisory)" - nothing below describes w7900-dual; it is only described in nightly-on-the-queue.md. Link that doc instead.

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

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

Agreed that "(below; advisory)" points at nothing in that doc. Not changing it in this PR, which is going to the merge queue as approved at d5233a6: the fix, a link to nightly-on-the-queue.md in place of "below", lands in #1063, which now owns the docs in this area.

in `e2e-selfhosted.yml` any more: W7900 is covered only by the scheduled queue
nightly's `w7900-dual` lane (below; advisory), not on `push`, `release/**` or
dispatch. Its first run, the 11-13 queue nightly
([run 43351651832](https://github.com/ROCm/rocm-cli/actions/runs/43351651832)), got capacity at once and finished `Done`, exit 0.

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.

Run 43351651832 shows an overall conclusion of failure (exit code 1 in "Run and publish"), and I couldn't confirm the w7900-dual lane itself "finished Done, exit 0". Please verify from the per-lane results, or soften/drop the run-specific claim, since it lands in durable docs.

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

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

Checked against the run's per-lane results rather than its overall conclusion. The run does conclude failure, from the blocking lanes: the lane matrix in the Run and publish job log (and the queue-run-results artifact) lists mi300x Failed, exit 1, and r9700s Failed, with no files collected, and both are in blocking: "mi300x,r9700s". In the same matrix w7900-dual is phase Done, exit 0, Exported, advisory, and its lane log collected 13 files. (mi325x, mi350p, mi350x and mi355x also failed, as advisory lanes.) So the claim in the docs is only that the lane ran and finished with exit 0, not that its scenarios were all green. https://github.com/ROCm/rocm-cli/actions/runs/43351651832

@tomastola
tomastola added this pull request to the merge queue Nov 13, 2026
Merged via the queue into main with commit 0aad1d2 Nov 13, 2026
41 checks passed
@tomastola
tomastola deleted the ci/retire-w7900-push-lane branch November 13, 2026 13:58
tomastola added a commit that referenced this pull request Nov 13, 2026
…same lines

Preparation for merging main into this branch without conflicts; the next
commits restore this change's own wording on top of the merge.

Signed-off-by: Tomas Saaristola <tsaarist@amd.com>
tomastola added a commit that referenced this pull request Nov 13, 2026
…ry ones out of the verdict

The e2e report names a lane of the shared GPU queue by the lane (a queue MI300X
lane is not the self-hosted one) and marks one the queue does not block on as
advisory. release-readiness leaves advisory rows out of its failure count and
still counts a blocking lane that came back with no result. xtask gains the
`e2e-queue-import` command, and the W7900 exemption in the per-PR/nightly
platform check goes, since #1066 removed the per-PR W7900 lane it exempted.

Signed-off-by: Tomas Saaristola <tsaarist@amd.com>
tomastola added a commit that referenced this pull request Nov 13, 2026
Retiring the self-hosted R9700, MI350P and W7900 nightly lanes would drop them
from the E2E-Support-Matrix and Release-Readiness wiki pages, and MI325X,
MI350X and MI355X, which only the queue runs, would never appear.
e2e-report-nightly now fetches the newest queue-run-results artifact of a main
run that finished in the last 24 hours (and its job log, for the tested branch
and each lane's gate), imports it, and opens the matrix with a Queue lanes
table. A missing, late or malformed queue run never fails the report: the page
says so instead.

The workflow contract pins the new steps and the native Linux preflight lane
counts for this change plus #1066 (four). The docs describe the queue import,
link the queue page instead of "(below; advisory)", and fix the "Of those"
wording in testing.md.

Signed-off-by: Tomas Saaristola <tsaarist@amd.com>
tomastola added a commit that referenced this pull request Nov 13, 2026
…same lines

Preparation for merging main into this branch without conflicts; the next
commits restore this change's own wording on top of the merge.

Signed-off-by: Tomas Saaristola <tsaarist@amd.com>
tomastola added a commit that referenced this pull request Nov 13, 2026
…ry ones out of the verdict

The e2e report names a lane of the shared GPU queue by the lane (a queue MI300X
lane is not the self-hosted one) and marks one the queue does not block on as
advisory. release-readiness leaves advisory rows out of its failure count and
still counts a blocking lane that came back with no result. xtask gains the
`e2e-queue-import` command, and the W7900 exemption in the per-PR/nightly
platform check goes, since #1066 removed the per-PR W7900 lane it exempted.

Signed-off-by: Tomas Saaristola <tsaarist@amd.com>
tomastola added a commit that referenced this pull request Nov 13, 2026
Retiring the self-hosted R9700, MI350P and W7900 nightly lanes would drop them
from the E2E-Support-Matrix and Release-Readiness wiki pages, and MI325X,
MI350X and MI355X, which only the queue runs, would never appear.
e2e-report-nightly now fetches the newest queue-run-results artifact of a main
run that finished in the last 24 hours (and its job log, for the tested branch
and each lane's gate), imports it, and opens the matrix with a Queue lanes
table. A missing, late or malformed queue run never fails the report: the page
says so instead.

The workflow contract pins the new steps and the native Linux preflight lane
counts for this change plus #1066 (four). The docs describe the queue import,
link the queue page instead of "(below; advisory)", and fix the "Of those"
wording in testing.md.

Signed-off-by: Tomas Saaristola <tsaarist@amd.com>
r0x0r added a commit that referenced this pull request Nov 16, 2026
One conflict: `apps/rocm/src/advised_commands.rs`. Both sides appended
entries to the same `NOT_INVOCATIONS` table, so the hunks collided on the
trailing `),` they share rather than on any disagreement.

#1067 added the `rocm fix --no-such-option; echo $?` entry, which belongs
to the "Deliberate negative examples" group already above it; this branch
added the ROCMAI-550 `device:`-value entries for README.md and
docs/manual-testing.md under their own comment. Both kept, with #1067's
entry restored to its group and this branch's block following it. All
three entries still name text that exists in those docs.

#1066's removal of the W7900 lane from e2e-selfhosted.yml is untouched by
this branch and carried through as main left it.

Signed-off-by: Roman Sirokov <roman.sirokov@amd.com>
rominf added a commit that referenced this pull request Nov 16, 2026
…ROCMAI-444)

#1066 removed e2e-gpu-w7900 from e2e-selfhosted.yml, the only lane the
contract test allowed to stay masked. With no masked lane left, the
per-workflow allow-list and its stale-entry check have nothing to hold,
so drop them: the contract test now fails on any line in a self-hosted
E2E lane of nightly.yml or e2e-selfhosted.yml that may set
continue-on-error to something other than false, and names each such
line with its lane.

The line scan, its pinned limits, the non-vacuity guard and the
e2e-report-nightly always() pin stay. A unit test drives the failure
message through a synthetic masked lane.

The docs and the nightly W7900 lane's comments no longer describe a
masked e2e-selfhosted.yml lane or a per-PR W7900 counterpart.

Signed-off-by: Roman Inflianskas <Roman.Inflianskas@amd.com>
r0x0r added a commit that referenced this pull request Nov 17, 2026
One conflict: `apps/rocm/src/advised_commands.rs`. Both sides appended
entries to the same `NOT_INVOCATIONS` table, so the hunks collided on the
trailing `),` they share rather than on any disagreement.

#1067 added the `rocm fix --no-such-option; echo $?` entry, which belongs
to the "Deliberate negative examples" group already above it; this branch
added the ROCMAI-550 `device:`-value entries for README.md and
docs/manual-testing.md under their own comment. Both kept, with #1067's
entry restored to its group and this branch's block following it. All
three entries still name text that exists in those docs.

#1066's removal of the W7900 lane from e2e-selfhosted.yml is untouched by
this branch and carried through as main left it.

Signed-off-by: Roman Sirokov <roman.sirokov@amd.com>
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.

3 participants