[ROCm][Bugfix] Ensure that the moe_wna16_gemm kernel is not built on ROCm platforms.

[SageMoore]

See above. This kernel was introduced in #13321.

[github-actions]

👋 Hi! Thank you for contributing to the vLLM project.

💬 Join our developer Slack at https://slack.vllm.ai to discuss your PR in #pr-reviews, coordinate on features in #feat- channels, or join special interest groups in #sig- channels.

Just a reminder: PRs would not trigger full CI run by default. Instead, it would only run fastcheck CI which starts running only a small and essential subset of CI tests to quickly catch errors. You can run other CI tests on top of those by going to your fastcheck build on Buildkite UI (linked in the PR checks section) and unblock them. If you do not have permission to unblock, ping simon-mo or khluu to add you in our Buildkite org.

Once the PR is approved and ready to go, your PR reviewer(s) can run CI to test the changes comprehensively before merging.

To run CI, PR reviewers can either: Add ready label to the PR or enable auto-merge.

🚀

[gshtras]

Confirming that this fixes the build. Thanks!

[mgoin]

Thank you Sage, LGTM. I think this kernels works on SM 70/75 so we should loosing the restriction later cc @jinzhen-lin but let's get the fix in now

[houseroad]

Shall we add a build test to cover such case in the follow up PR?

Ideally, this should be caught by CI directly.

[hongxiayang]

This is needed to fix ROCm build issue

[hongxiayang]

it fixed my build issue

[hongxiayang]

Shall we add a build test to cover such case in the follow up PR?

Ideally, this should be caught by CI directly.

I agree.

[SageMoore]

Shall we add a build test to cover such case in the follow up PR?

Ideally, this should be caught by CI directly.

Looks like the AMD job was not run on #13321 which is why the build error slipped through the cracks.

Unfortunately, the AMD job has been red for quite some time and we don't want to add additional noise to inflight PRs. We've made decent strides towards getting that build green, but there's more work to do. If you are interested in contributing to this effort, feel free to reach out to me on the vllm slack and I can provide some more context. There's nothing really hard here, we just need to grind through all of the failures.