Earlier this year, there was a discussion about the understated
--status option. This option causes runtest to exit with an exit code
of 1 ("failure" to the shell) if an error is encountered in any of the
Tcl scripts. The thread starts here:
http://lists.gnu.org/archive/html/dejagnu/2016-01/msg
Hi David,
On Fri, Jan 22, 2016 at 04:53:00PM -0500, David Malcolm wrote:
> My tests use dejagnu.h to write "PASSED" etc lines, some of which are
> very long. They're sometimes being truncated by fixed_host_execute when
> re-emitted as PASS results, so e.g.
> PASSED: test-combination.c.exe iterat
In January 2004, Michael Chastain sent a DejaGnu wishlist:
https://lists.gnu.org/archive/html/dejagnu/2004-01/msg00072.html
I have just implemented this one in the following patch:
"When the compiler produces error messages, default_target_compile
calls "verbose -log ...". There is no
> > On 09/28/2014 10:36 AM, Maxim Kuvyrkov wrote:
> >> This patch fixes an issue that rsh_exec does bails on tests in
> > just 10sec, even when board specifies a longer timeout. The
> > problem is that lib/rsh.exp:rsh_exec (which is called via
> > remote.exp:remote_exec) reads its timeout from gl
Hi Maxim
(Reply in under two years!)
What is your means of communicating with the remote target? If you
are using ssh, you could set SendEnv on the client side and AcceptEnv
on the server side. Would this remove any need for harness changes?
Cheers, Ben
___
Hi Dominik
Thanks for tracking this down, in the end.
> Any bytes past the initial 512000 bytes seem to be discarded. I can
> fix my immediate problem by increasing this value. Maybe this
> should be configurable on the command line?
I think the real answer is to try and eliminate this arbitra
