[MoE Refactor] Add Temporary Integration Tests - H100/B200

[robertgshaw2-redhat]

Purpose

• add ci job to validate MoE refactor
• this is very compute intensive and duplicative, so this is a temporary job that I will run on my PRs

---

Essential Elements of an Effective PR Description Checklist

• The purpose of the PR, such as "Fix some issue (link existing issues this PR will resolve)".
• The test plan, such as providing test command.
• The test results, such as pasting the results comparison before and after, or e2e results
• (Optional) The necessary documentation update, such as updating supported_models.md and examples for a new model.
• (Optional) Release notes update. If your change is user facing, please update the release notes draft in the Google Doc.

[gemini-code-assist]

Code Review

This pull request adds H100 integration tests for MoE refactoring. My review found several critical and high-severity issues, primarily related to test configuration.

• The new Buildkite pipeline step is misconfigured, pointing to the wrong test script, configuration file, and using an incorrect tensor parallelism size.
• Several YAML configuration files contain errors, such as typos in environment variable names, invalid syntax, conflicting settings (e.g., enabling both DeepGEMM and FlashInfer), and mismatches between filenames and their content (e.g., a 'cutlass' test enabling 'marlin').
• The main test list file (config-h100.txt) is incomplete and omits several of the newly added test configurations, meaning they would not be executed.

These issues need to be addressed to ensure the new integration tests run correctly and validate the intended configurations.

[robertgshaw2-redhat]

I unblocked the job

[robertgshaw2-redhat]

/gemini review

[gemini-code-assist]

Code Review

This pull request introduces temporary integration tests for the MoE refactor, targeting H100 and B200 GPUs. It adds new Buildkite pipeline steps and a comprehensive set of YAML configuration files for various test scenarios. My review identified a critical syntax error in one of the YAML configuration files that would cause a CI job to fail, and a misconfiguration in another CI job where an incorrect test suite was specified. Addressing these issues will ensure the new temporary tests run correctly.

[gemini-code-assist]

This line contains only indented whitespace, which is invalid YAML syntax in this context. This will cause the YAML parser to fail and crash the test run. Please remove this line to fix the syntax.

[gemini-code-assist]

The B200 integration test is configured to use the config-h100.txt file. This appears to be a copy-paste error and will cause the H100 test suite to run on B200 hardware, instead of the intended B200-specific tests defined in config-b200.txt.

    - pytest -s -v evals/gsm8k/test_gsm8k_correctness.py --config-list-file=evals/gsm8k/configs/moe-refactor/config-b200.txt

[mergify]

Hi @robertgshaw2-redhat, the pre-commit checks have failed. Please run:

uv pip install pre-commit
pre-commit install
pre-commit run --all-files

Then, commit the changes and push to your branch.

For future commits, pre-commit will run automatically on changed files before each commit.

Tip

Is mypy or markdownlint failing?

mypy and markdownlint are run differently in CI. If the failure is related to either of these checks, please use the following commands to run them locally:

# For mypy (substitute "3.10" with the failing version if needed)
pre-commit run --hook-stage manual mypy-3.10
# For markdownlint
pre-commit run --hook-stage manual markdownlint

[mgoin]

nice work!