Skip to content

'lit :: progress-bar.py' test is flaky #72022

Open
@mgorny

Description

@mgorny

I thought we had a bug for this but couldn't find one. The test fails sometimes, especially on systems with high load. IIUC it prints one dot too many but I have no clue why.

******************** TEST 'lit :: progress-bar.py' FAILED ********************
Exit Code: 1

Command Output (stdout):
--
# RUN: at line 3
not env -u FILECHECK_OPTS "/tmp/portage/dev-python/lit-18.0.0_pre20231111/work/llvm/utils/lit-python3_12/install/usr/bin/python3" /tmp/
portage/dev-python/lit-18.0.0_pre20231111/work/llvm/utils/lit/lit.py -j1 --order=lexical -s Inputs/progress-bar > /tmp/portage/dev-pyth
on/lit-18.0.0_pre20231111/work/llvm/utils/lit/tests/Output/progress-bar.py.tmp.out
# executed command: not env -u FILECHECK_OPTS /tmp/portage/dev-python/lit-18.0.0_pre20231111/work/llvm/utils/lit-python3_12/install/usr
/bin/python3 /tmp/portage/dev-python/lit-18.0.0_pre20231111/work/llvm/utils/lit/lit.py -j1 --order=lexical -s Inputs/progress-bar
# RUN: at line 4
FileCheck < /tmp/portage/dev-python/lit-18.0.0_pre20231111/work/llvm/utils/lit/tests/Output/progress-bar.py.tmp.out /tmp/portage/dev-py
thon/lit-18.0.0_pre20231111/work/llvm/utils/lit/tests/progress-bar.py
# executed command: FileCheck /tmp/portage/dev-python/lit-18.0.0_pre20231111/work/llvm/utils/lit/tests/progress-bar.py
# .---command stderr------------
# | /tmp/portage/dev-python/lit-18.0.0_pre20231111/work/llvm/utils/lit/tests/progress-bar.py:9:10: error: CHECK: expected string not fo
und in input
# | # CHECK: FAIL: progress-bar :: test-2.txt (2 of 4)
# |          ^
# | <stdin>:6:21: note: scanning from here
# | Testing: 0.. 10.. 20.
# |                     ^
# | <stdin>:7:1: note: possible intended match here
# | FAIL: progress-bar :: test-3.txt (3 of 4)
# | ^
# | 
# | Input file: <stdin>
# | Check file: /tmp/portage/dev-python/lit-18.0.0_pre20231111/work/llvm/utils/lit/tests/progress-bar.py
# | 
# | -dump-input=help explains the following input dump.
# | 
# | Input was:
# | <<<<<<
# |            1: -- Testing: 4 tests, 1 workers -- 
# |            2: Testing:  
# |            3: FAIL: progress-bar :: test-1.txt (1 of 4) 
# |            4: Testing: 0.. 10 
# |            5: FAIL: progress-bar :: test-2.txt (2 of 4) 
# |            6: Testing: 0.. 10.. 20. 
# | check:9'0                         X~ error: no match found
# |            7: FAIL: progress-bar :: test-3.txt (3 of 4) 
# | check:9'0     ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
# | check:9'1     ?                                          possible intended match
# |            8: Testing: 0.. 10.. 20.. 30.. 40.. 50.. 60 
# | check:9'0     ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
# |            9: FAIL: progress-bar :: test-4.txt (4 of 4) 
# | check:9'0     ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
# |           10: Testing: 0.. 10.. 20.. 30.. 40.. 50.. 60.. 70.. 80.. 90..  
# | check:9'0     ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
# |           11: ******************** 
# | check:9'0     ~~~~~~~~~~~~~~~~~~~~~
# |           12: Failed Tests (4): 
# | check:9'0     ~~~~~~~~~~~~~~~~~~
# |            .
# |            .
# |            .
# | >>>>>>
# `-----------------------------
# error: command failed with exit status: 1

--

********************

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions