PTQ-Level Efficiency, QAT-Level Accuracy | 训练后量化的效率,量化感知训练的精度
Stabilize MoE prefill accuracy test (#2060)
Dong, Bo98ad266f2e86
diff --git a/.azure-pipelines/ark-unit-test.yml b/.azure-pipelines/ark-unit-test.ymlindex e7af1b242..f9e2b3d0a 100644--- a/.azure-pipelines/ark-unit-test.yml+++ b/.azure-pipelines/ark-unit-test.yml@@ -61,7 +61,7 @@ stages:- ${{ each torchVersion in split(parameters.torchVersions, ',') }}:- job: TestArk_py${{ replace(trim(pythonVersion), '.', '') }}_torch${{ replace(replace(trim(torchVersion), '.', ''), '+', '_') }}displayName: "Test py${{ trim(pythonVersion) }} torch${{ trim(torchVersion) }}"- pool: INTEL-CPU+ pool: B60variables:condaName: "kernel_binary_test_py${{ replace(trim(pythonVersion), '.', '') }}$(NODE_LABEL)"steps:@@ -107,7 +107,7 @@ stages:jobs:- job: PublishDistdisplayName: Publish all dist to ${{ parameters.publishTarget }}- pool: B60+ pool: INTEL-CPUsteps:- checkout: nonediff --git a/auto_round_extension/ark/test/test_moe_prefill_accuracy.py b/auto_round_extension/ark/test/test_moe_prefill_accuracy.pyindex c8c1ee168..e9f7ca859 100644--- a/auto_round_extension/ark/test/test_moe_prefill_accuracy.py+++ b/auto_round_extension/ark/test/test_moe_prefill_accuracy.py@@ -226,6 +226,47 @@ class TestMoEGemmPrefillAccuracy:if hasattr(torch, "xpu") and torch.xpu.is_available():torch.xpu.manual_seed_all(0)+ @pytest.fixture(autouse=True)+ def _xpu_cleanup_between_tests(self):+ """Release the XPU allocator cache before and after every test.++ The quantized prefill paths allocate ``torch.empty`` buffers -- the+ ``[total_tokens, N]`` output and (for the dequant path) a large+ ``[E, K, N]`` scratch workspace -- and the grouped GEMM only writes the+ token/expert rows it is actually dispatched for. Any element it does not+ overwrite reads back whatever bytes the caching allocator handed out.++ Run in isolation the accumulator starts empty, so those buffers come from+ fresh device pages that read back as zeros and the comparison passes.+ Run as part of the full suite, the preceding XPU test files+ (``test_matmul``, ``test_moe``, ``test_moe_decode_perf``, ...) leave the+ allocator holding a large, *non-zero* working set; the next ``torch.empty``+ here reuses one of those dirty blocks and the stale bytes surface as a+ handful of wildly-wrong outputs. That is the classic "passes in isolation,+ fails only in the full suite" symptom (observed on+ ``test_accuracy_int4``).++ Every other XPU test file in this directory already brackets its tests+ with ``torch.xpu.empty_cache()`` for exactly this reason (see+ ``_xpu_cleanup_between_tests`` in ``test_moe_decode_perf.py`` and the+ per-test ``empty_cache`` calls in ``test_matmul.py`` /+ ``test_weightonly.py``). Mirror that here so each accuracy test starts+ from a clean allocator state regardless of what ran before it.+ """+ self._release_xpu_memory()+ try:+ yield+ finally:+ self._release_xpu_memory()++ @staticmethod+ def _release_xpu_memory():+ """Synchronize and free cached XPU memory (no-op when XPU is absent)."""+ if hasattr(torch, "xpu") and torch.xpu.is_available():+ torch.xpu.synchronize()+ if hasattr(torch.xpu, "empty_cache"):+ torch.xpu.empty_cache()+@pytest.mark.parametrize("dtype", [torch.float16, torch.bfloat16])def test_accuracy_fp(self, dtype):for label, E, tpe, N, K in PREFILL_SHAPES: