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

[llvmlistbot at llvm.org]

llvmbot wrote:


<!--LLVM PR SUMMARY COMMENT-->

@llvm/pr-subscribers-mlir

Author: Jared Hoberock (jaredhoberock)

<details>
<summary>Changes</summary>

#<!-- -->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.

---
Full diff: https://github.com/llvm/llvm-project/pull/190702.diff


1 Files Affected:

- (modified) mlir/test/Integration/GPU/CUDA/async.mlir (+5-2) 


``````````diff
diff --git a/mlir/test/Integration/GPU/CUDA/async.mlir b/mlir/test/Integration/GPU/CUDA/async.mlir
index 5acadd61f432c..3e45b5af5826c 100644
--- a/mlir/test/Integration/GPU/CUDA/async.mlir
+++ b/mlir/test/Integration/GPU/CUDA/async.mlir
@@ -8,8 +8,11 @@
 // RUN:   --shared-libs=%mlir_cuda_runtime \
 // RUN:   --shared-libs=%mlir_async_runtime \
 // RUN:   --shared-libs=%mlir_runner_utils \
-// RUN:   --entry-point-result=void -O0 \
-// RUN: | FileCheck %s
+// RUN:   --entry-point-result=void -O0
+// 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() {
   %c0    = arith.constant 0 : index

``````````

</details>


https://github.com/llvm/llvm-project/pull/190702