[PATCH] Update .gitignore

2015-05-14 Thread Filipe Brandenburger
Tested by running `./configure --enable-maintainer-mode' and then the sequence `make && make check && make distcheck' and confirming that the `git status' output did not show any untracked files. Signed-off-by: Filipe Brandenburger --- .gitignore | 21 - 1 file changed, 20 in

[PATCH] Fix docs to remove stray }'s and @samp{...}

2015-05-14 Thread Filipe Brandenburger
These are probably problems introduced when these documents were originally converted from .texi to DocBook. I traced them back to the first revision in git (from 2001) which introduced SGML files and already had these problems. * doc/dejagnu.xml: Fix typos such as stray }'s and @samp{...}

[PATCH] Fix docs to remove stray }'s and @samp{...}

2015-05-14 Thread Filipe Brandenburger
Hi Ben, While working on the docs for --log_dialog, I noticed a stray `}' in the previous option. When I went to fix it, I noticed that was not the only place. Looks like these were introduced when these docs were originally converted, I assume from .texi to DocBook, I traced these issues back to

[PATCH v4 1/1] Introduce new --log_dialog option to emit expect output to stdout

2015-05-14 Thread Filipe Brandenburger
* runtest.exp (runtest): Introduce new --log_dialog option. This option is useful when running dejagnu tests on an automated environment where only test stdout is accessible after a test run. The expect output (usually saved in *.log files) is useful to debug test failures which often are not

[PATCH v3 1/1] Introduce new --log_dialog option to emit expect output to stdout

2015-05-14 Thread Filipe Brandenburger
* runtest.exp (runtest): Introduce new --log_dialog option. This option is useful when running dejagnu tests on an automated environment where only test stdout is accessible after a test run. The expect output (usually saved in *.log files) is useful to debug test failures which often are not

Re: [PATCH 0/1] New option for runtest to log_user to stdout

2015-05-14 Thread Filipe Brandenburger
Hi Ben, On Thu, May 14, 2015 at 5:20 PM, Ben Elliston wrote: > On Wed, May 06, 2015 at 03:04:09PM -0700, Filipe Brandenburger wrote: >> So, I'm proposing adding a new option (--log_user is my suggestion, >> but feel free to pick something else) to allow enabling "log_user" >> expect output to std

Re: [PATCH 0/1] New option for runtest to log_user to stdout

2015-05-14 Thread Ben Elliston
On Wed, May 06, 2015 at 03:04:09PM -0700, Filipe Brandenburger wrote: > So, I'm proposing adding a new option (--log_user is my suggestion, > but feel free to pick something else) to allow enabling "log_user" > expect output to stdout without the need to increase verbosity. I don't have a problem