Skip to content

test: remove source guard tests - #87

Open
Kur0x wants to merge 2 commits into
mainfrom
codex/remove-source-guards
Open

test: remove source guard tests#87
Kur0x wants to merge 2 commits into
mainfrom
codex/remove-source-guards

Conversation

@Kur0x

@Kur0x Kur0x commented Jul 29, 2026

Copy link
Copy Markdown
Member

Summary

  • remove source-text guard tests from checker, collectives, comm, DataAsFlag, EP, memory, SDMA, and UDMA
  • remove their CMake, test-runner, CI, and documentation wiring while retaining behavioral and compile tests
  • rename the EP host mode and collectives profiling preflight, and keep memory installation valid when no demo target is built
  • publish sealed controller v5 so the trusted blue gate no longer invokes removed test binaries

Validation

  • PR CI Host Checks passed
  • PR CI NPU Gate passed in 12m1s, including the complete required 8-card gate
  • PR Gate passed
  • sealed controller v5 was staged, activated on blue, and passed scripts/ci/provision/verify.sh
  • standalone CI CTest: 5/5 passed
  • EP host CTest: 2/2 passed
  • DataAsFlag header CTest: 1/1 passed
  • comm log and spdlog compile binaries passed
  • affected checker shim-events and trace-adapter-generator binaries passed locally; the Linux top-level checker suite passed in NPU Gate
  • vLLM patch tests: 3 passed
  • collective profile-report tests: 25 passed
  • shell syntax, git diff --check, deleted-test reference scan, and source/guard filename scan passed

No NPU data-plane implementation behavior is changed.

@Kur0x
Kur0x requested a review from a team as a code owner July 29, 2026 07:57

@chatgpt-codex-connector chatgpt-codex-connector Bot 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.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: e7f5a58932

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

Comment on lines -193 to -195
void TestInt32PatternHasNoKnownCollisions()
{
using TileXRCollectivesTest::CanUseCollisionFreeInt32Pattern;

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

P2 Badge Preserve the collision-free pattern unit coverage

This function is an executable unit test, not a source guard: it verifies that the INT32 patterns used by the correctness and performance tools uniquely identify rank/index payloads. When ExpectedAllGatherValue, ExpectedAllToAllValue, or their bounds change, a collision can let a misplaced collective payload compare equal to the expected value; the remaining host suite has no equivalent check, while the consumers require NPU execution. Move this test into a dedicated unit target rather than deleting it with the source-inspection checks.

Useful? React with 👍 / 👎.

assert "python3 \"${SCRIPT_DIR}/smoke_collectives.py\"" not in source


def test_smoke_launcher_accepts_preflight_sentinel_with_plugin_stdout(tmp_path) -> None:

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

P2 Badge Retain the smoke launcher behavior test

This deleted test actually executes run_tilexr_collectives_smoke.sh; it is not a source guard. In environments where the selected Python interpreter or an auto-loaded plugin writes informational output before the preflight sentinel, it verifies that the launcher still accepts the interpreter and reaches the smoke command. The remaining test_vllm_collectives_patch.py tests adapter routing only, so deleting this file removes the sole regression test for that launcher behavior; move the test to a behavioral test module instead.

Useful? React with 👍 / 👎.

@@ -308,9 +284,6 @@ foreach(_tilexr_collectives_link_target
TileXRAddAscendRpathLink(${_tilexr_collectives_link_target})

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

P2 Badge Update the documented collectives CTest coverage

After these source-oriented targets are removed, the recommended CTest command no longer checks collectives scripts, documentation, or general tool wiring, but README.md lines 314–320 and tests/collectives/README.md lines 18–19 still explicitly claim that it does. A contributor can therefore run the documented validation successfully and incorrectly report coverage that is no longer present; update those validation descriptions to list only the remaining header, library, and behavioral checks.

Useful? React with 👍 / 👎.

@chatgpt-codex-connector chatgpt-codex-connector Bot 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.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: d6de9e3b77

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

Comment on lines 62 to 63
"${cmake_bin}" --build "${build_dir}" --target \
test_tilexr_collectives_kernel_ownership \
test_tilexr_collectives_tools_sources \
tilexr_collective_perf -j"${build_jobs}"

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

P2 Badge Correct the multi-host preflight coverage claim

When an operator follows docs/COLLECTIVES_MULTIHOST_PROFILING.md lines 88–94 and runs prepare, this changed target list builds only tilexr_collective_perf, while run_preflight now runs only the profile-report tests. The runbook still says that prepare performs guard checks on every peer, so a successful preparation can be reported as coverage that no longer occurred; update the runbook to describe the reduced preflight or restore equivalent checks.

Useful? React with 👍 / 👎.

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.

1 participant