[MLIR][test] Re-disable FileCheck on async.mlir integration test (#190702)

#190563 re-enabled FileCheck on `Integration/GPU/CUDA/async.mlir`, but
the buildbot has shown intermittent wrong-output failures
([example](https://lab.llvm.org/buildbot/#/builders/116/builds/27026)):
the test produces `[42, 42]` instead of the expected `[84, 84]`.

This wrong-output flakiness is distinct from the cleanup-time
`cuModuleUnload` errors that #190563 actually fixes — it's the
underlying issue tracked by #170833. The merged commit message for
#190563 incorrectly says `Fixes #170833`; that issue should be reopened,
since the cleanup-error fix doesn't address the wrong-output behavior.

This PR puts the test back in its previously-disabled state. The runtime
cleanup fix in #190563 is unaffected.
This commit is contained in:
Jared Hoberock 2026-04-06 18:14:56 -05:00 committed by GitHub
parent aedd4e0850
commit 90ec5f2f62
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194

View File

@ -8,8 +8,11 @@
// RUN: --shared-libs=%mlir_cuda_runtime \ // RUN: --shared-libs=%mlir_cuda_runtime \
// RUN: --shared-libs=%mlir_async_runtime \ // RUN: --shared-libs=%mlir_async_runtime \
// RUN: --shared-libs=%mlir_runner_utils \ // RUN: --shared-libs=%mlir_runner_utils \
// RUN: --entry-point-result=void -O0 \ // RUN: --entry-point-result=void -O0
// RUN: | FileCheck %s // RUN:
// This test is overly flaky right now and needs investigation, skipping FileCheck.
// See: https://github.com/llvm/llvm-project/issues/170833
// DISABLED: | FileCheck %s
func.func @main() { func.func @main() {
%c0 = arith.constant 0 : index %c0 = arith.constant 0 : index