On 11:06, Ville Skyttä wrote:
Just for kicks, did you try other TERM values, for example vt110?
Using these commands
- interactive: ./runUnit _known_hosts_real.exp --debug
- cron/batch: ./runUnit _known_hosts_real.exp --debug /dev/tty40
These are the results for other terminal settings:
On Thursday 19 November 2009, Freddy Vulto wrote:
Err, TERM=linux also causes errors when tests are run via cron.
Reset TERM=dummy.
Workaround is to do a CRON=x from within the cron job and only set
TERM=dummy when not run via cron. See git commit 2a506ec3f
Just for kicks, did you try other
On Monday 09 November 2009, Freddy Vulto wrote:
On 12:08, Ville Skyttä wrote:
1) ./runCompletion (alone, or with $something.exp) always prints out:
ERROR Unexpected output from bash command bash --rcfile config/bashrc:
By adding some send_user's to assert_bash_exec I found
Hello,
I have a few questions about and some failures in the test suite:
1) ./runCompletion (alone, or with $something.exp) always prints out:
ERROR Unexpected output from bash command bash --rcfile config/bashrc:
By adding some send_user's to assert_bash_exec I found that the
