Open
Description
The middle half repetition mode test is flaky on the buildbots that run it (https://lab.llvm.org/buildbot/#/builders/258/builds/13464):
******************** TEST 'LLVM :: tools/llvm-exegesis/X86/latency/middle-half.s' FAILED ********************
Exit Code: 1
Command Output (stderr):
--
RUN: at line 5: /localdisk2/buildbot/llvm-worker/clang-cmake-x86_64-avx512-linux/stage1/bin/llvm-exegesis -mtriple=x86_64-unknown-unknown -mode=latency -opcode-name=ADD64rr -repetition-mode=middle-half-duplicate | /localdisk2/buildbot/llvm-worker/clang-cmake-x86_64-avx512-linux/stage1/bin/FileCheck /localdisk2/buildbot/llvm-worker/clang-cmake-x86_64-avx512-linux/llvm/llvm/test/tools/llvm-exegesis/X86/latency/middle-half.s
+ /localdisk2/buildbot/llvm-worker/clang-cmake-x86_64-avx512-linux/stage1/bin/FileCheck /localdisk2/buildbot/llvm-worker/clang-cmake-x86_64-avx512-linux/llvm/llvm/test/tools/llvm-exegesis/X86/latency/middle-half.s
+ /localdisk2/buildbot/llvm-worker/clang-cmake-x86_64-avx512-linux/stage1/bin/llvm-exegesis -mtriple=x86_64-unknown-unknown -mode=latency -opcode-name=ADD64rr -repetition-mode=middle-half-duplicate
RUN: at line 6: /localdisk2/buildbot/llvm-worker/clang-cmake-x86_64-avx512-linux/stage1/bin/llvm-exegesis -mtriple=x86_64-unknown-unknown -mode=latency -opcode-name=ADD64rr -repetition-mode=middle-half-loop | /localdisk2/buildbot/llvm-worker/clang-cmake-x86_64-avx512-linux/stage1/bin/FileCheck /localdisk2/buildbot/llvm-worker/clang-cmake-x86_64-avx512-linux/llvm/llvm/test/tools/llvm-exegesis/X86/latency/middle-half.s
+ /localdisk2/buildbot/llvm-worker/clang-cmake-x86_64-avx512-linux/stage1/bin/FileCheck /localdisk2/buildbot/llvm-worker/clang-cmake-x86_64-avx512-linux/llvm/llvm/test/tools/llvm-exegesis/X86/latency/middle-half.s
+ /localdisk2/buildbot/llvm-worker/clang-cmake-x86_64-avx512-linux/stage1/bin/llvm-exegesis -mtriple=x86_64-unknown-unknown -mode=latency -opcode-name=ADD64rr -repetition-mode=middle-half-loop
/localdisk2/buildbot/llvm-worker/clang-cmake-x86_64-avx512-linux/llvm/llvm/test/tools/llvm-exegesis/X86/latency/middle-half.s:8:10: error: CHECK: expected string not found in input
# CHECK: - { key: latency, value: {{[0-9.]*}}, per_snippet_value: {{[0-9.]*}}
^
<stdin>:1:1: note: scanning from here
---
^
<stdin>:14:2: note: possible intended match here
- { key: latency, value: -0.0024, per_snippet_value: -0.0024, validation_counters: {} }
^
Input file: <stdin>
Check file: /localdisk2/buildbot/llvm-worker/clang-cmake-x86_64-avx512-linux/llvm/llvm/test/tools/llvm-exegesis/X86/latency/middle-half.s
-dump-input=help explains the following input dump.
Input was:
<<<<<<
1: ---
check:8'0 X~~~ error: no match found
2: mode: latency
check:8'0 ~~~~~~~~~~~~~~
3: key:
check:8'0 ~~~~~
4: instructions:
check:8'0 ~~~~~~~~~~~~~~~
5: - 'ADD64rr R11 R11 RSI'
check:8'0 ~~~~~~~~~~~~~~~~~~~~~~~~~
6: config: ''
check:8'0 ~~~~~~~~~~~~
.
.
.
9: - 'RSI=0x0'
check:8'0 ~~~~~~~~~~~~~
10: cpu_name: cascadelake
check:8'0 ~~~~~~~~~~~~~~~~~~~~~~
11: llvm_triple: x86_64-unknown-unknown
check:8'0 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
12: min_instructions: 10000
check:8'0 ~~~~~~~~~~~~~~~~~~~~~~~~
13: measurements:
check:8'0 ~~~~~~~~~~~~~~
14: - { key: latency, value: -0.0024, per_snippet_value: -0.0024, validation_counters: {} }
check:8'0 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
check:8'1 ? possible intended match
15: error: ''
check:8'0 ~~~~~~~~~~
16: info: Repeating a single implicitly serial instruction
check:8'0 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
17: assembled_snippet: 49BB000000000000000048BE000000000000000049B8020000000000000066904901F34901F34983C0FF75F4C349BB000000000000000048BE000000000000000049B8020000000000000066904901F34901F34983C0FF75F4C3
check:8'0 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
18: ...
check:8'0 ~~~~
>>>>>>
--
********************
Seems like the negative sign is throwing off the check line. Probably will throw up a quick fix (like setting a retry count) to fix this, but this shouldn't be occurring in the first place and more debugging there will be needed.