Skip to content

render::tui test blocks indefinitely on Windows #54

@EliahKagan

Description

@EliahKagan

#52 fixed a bug on CI where no Windows tests were ever run, due to the errant fragment progress-tree" (with an unmatched ") being parsed in a way that it caused all tests to be filtered out.

Actually running the Windows tests on CI revealed that the render::tui test blocks indefinitely, as seen in this test run, where I allowed it to continue running until the job was automatically cancelled due to how long it had been running.

cargo test reported that it took over 60 seconds, but to be clear, it then continued running for a number of hours before GHA cancelled the job. I also did try running it other times to ensure that it wasn't due to an intermittent problem on CI (this was actually the second run).

I worked around this in #52 by skipping that test. All other tests passed, so I merged the PR, since this seems to have been a long-standing probem that was surfaced but not caused by actually running the tests on Windows. So I figured this should have its own issue, if it doesn't already.

Metadata

Metadata

Assignees

No one assigned

    Labels

    questionFurther information is requested

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions