You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
I'm using tui-rs & crossterm for my gpg-tui project and I have a test where I want to test if the TUI is functional by executing only the init functions. I'm not sure it's a good idea to attempt to test this case but I'm curious since it fails on GitHub actions but works on my setup. I've read from some of the issues here that it might be about tty and I very much like to know why/how this happens.
To Reproduce
Steps to reproduce the behavior:
Run the following test suite on a CI with cargo test:
Error: IoError(Os { code: 6, kind: Other, message: "No such device or address" })
thread 'tests::test_tui' panicked at 'assertion failed: `(left == right)`
left: `1`,
right: `0`: the test returned a termination value with a non-zero status code (1) which indicates a failure', /rustc/e1884a8e3c3e813aada8254edfa120e85bf5ffca/library/test/src/lib.rs:193:5
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
test tests::test_tui ... FAILED
failures:
failures:
tests::test_tui
test result: FAILED. 0 passed; 1 failed; 0 ignored; 0 measured; 0 filtered out
Expected behavior
Passed tests.
OS runs-on: ubuntu-latest
The text was updated successfully, but these errors were encountered:
A CI test suite is not able to use TTY device. Therefore it throws a 'No such device address error. And CI terminal is different from a desktop terminal.
Describe the bug
I'm using tui-rs & crossterm for my gpg-tui project and I have a test where I want to test if the TUI is functional by executing only the init functions. I'm not sure it's a good idea to attempt to test this case but I'm curious since it fails on GitHub actions but works on my setup. I've read from some of the issues here that it might be about
tty
and I very much like to know why/how this happens.To Reproduce
Steps to reproduce the behavior:
cargo test
:or without
tui
stuff (result is the same):Expected behavior
Passed tests.
OS
runs-on: ubuntu-latest
The text was updated successfully, but these errors were encountered: