Skip to content

Conversation

@jdenny-ornl
Copy link
Collaborator

The test was added by b8ef25a. It failed on at least the following bots, but the failure did not reproduce on my test machines or in pre-commit CI:

d69e701 did not fix the failure. Hopefully this will.

The test was added by b8ef25a. It
failed on at least the following bots, but the failure did not reproduce
on my test machines or in pre-commit CI:

- https://lab.llvm.org/buildbot/#/builders/190/builds/31643
- https://lab.llvm.org/buildbot/#/builders/65/builds/25949
- https://lab.llvm.org/buildbot/#/builders/154/builds/24417

d69e701 did not fix the failure.
Hopefully this will.
@jdenny-ornl jdenny-ornl merged commit 8380a48 into main Nov 25, 2025
6 of 10 checks passed
@jdenny-ornl jdenny-ornl deleted the users/jdenny-ornl/pr-167792-fixup2 branch November 25, 2025 17:33
@llvmbot
Copy link
Member

llvmbot commented Nov 25, 2025

@llvm/pr-subscribers-llvm-transforms

Author: Joel E. Denny (jdenny-ornl)

Changes

The test was added by b8ef25a. It failed on at least the following bots, but the failure did not reproduce on my test machines or in pre-commit CI:

d69e701 did not fix the failure. Hopefully this will.


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

1 Files Affected:

  • (modified) llvm/test/Transforms/LoopVectorize/vectorize-zero-estimated-trip-count.ll (+1)
diff --git a/llvm/test/Transforms/LoopVectorize/vectorize-zero-estimated-trip-count.ll b/llvm/test/Transforms/LoopVectorize/vectorize-zero-estimated-trip-count.ll
index c91a764681d20..8cde10350bd87 100644
--- a/llvm/test/Transforms/LoopVectorize/vectorize-zero-estimated-trip-count.ll
+++ b/llvm/test/Transforms/LoopVectorize/vectorize-zero-estimated-trip-count.ll
@@ -2,6 +2,7 @@
 ; LoopVectorize behavior while it tries to create runtime memory checks inside
 ; an outer loop.
 
+; REQUIRES: x86-registered-target
 ; RUN: opt -passes=loop-vectorize -S %s | FileCheck %s
 
 target datalayout = "e-m:e-i64:64-f80:128-n8:16:32:64-S128"

@jdenny-ornl
Copy link
Collaborator Author

@dyung This seems to have fixed those failures. Thanks for the suggestion.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants