mgunyho
commented
1 year ago Huh, thanks for the report. So seems like that is coming from the stderr of the app, and not from any of the test code. Is it possible to run just the app in the chroot environment with something like
# so that the environment is similar to the tests
$ mkdir /tmp/test
$ cd /tmp/test
# The PWD can maybe left out? Not sure. But this is effectively what I do in the test.
$ PWD=/tmp/test /path/to/tere &> test-out.txt
<press ctrl-c or esc to exit if necessary>
$ PWD=/tmp/test /path/to/tere 2> test-out-stderr.txt 1> test-out-stdout.txt
<press ctrl-c or esc to exit if necessary>Could you do this and tell me what's in the txt files, including control codes? Or what is the output of the app if you just run it without redirecting the output?
Another option is to try to add a test to tests/cli.rs that prints the full output without stripping the alternate screen:
#[test]
fn dummy() -> Result<(), RexpectError> {
let mut proc = run_app_with_cmd(get_cmd_no_first_run_prompt());
proc.send_control('c')?;
proc.writer.flush()?;
let output = proc.exp_eof()?;
println!("{:?}", output);
assert!(false);
}And check the stdout of that, does it have some more info than "Error: Io(Os { code: 11, ... } )"
orhun
ProducerMatt
Integration tests were added in the last release, more specifically: https://github.com/mgunyho/tere/commit/70d2686e3ad5bd950e6137dd755a0d7e59b42dc1
I'm getting the following test failures in a clean chroot build:
I couldn't figure out why this is happening so I thought it'd better to report here.
As a workaround, I tried skipping the integration tests and using
--libbut goterror: no library targets found in package tere.