gump-general mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "BAZLEY, Sebastian" <>
Subject RE: Missing [GUMP] nags for Jmeter
Date Fri, 20 Feb 2004 17:21:49 GMT
>-----Original Message-----
>From: Stefan Bodewig []
>Sent: 20 February 2004 16:24
>Subject: Re: Missing [GUMP] nags for Jmeter
>On Fri, 20 Feb 2004, Adam R. B. Jack <> wrote:
>> [BTW: Ought Gumpy respect the regexp? Traditional ran perl on a log,
>> Gumpy works of the exit code. I've been thinking not...]
>This feature has been used in the past to send nags about specific
>failures to a different project for example.  I think it has been a
>NPE in FOP that was caused by a bug in Xalan and we used a regexp to
>nag xalan-dev instead of (or in addition to) fop-dev.

The problem with relying on the exit code is that the build file may do
something else after the test has failed. In Jmeter's case it types the log
file, which is probably why the exit code is OK.

Perhaps it might also be useful to support nagging on the basis of a special
property, which the build file could set? This could be an alternative to
the <regex

Perhaps Gumpy should print a warning for any (un|differently)-implemented
features ...



This e-mail and the documents attached are confidential and intended solely
for the addressee; it may also be privileged. If you receive this e-mail in
error, please notify the sender immediately and destroy it. As its integrity
cannot be secured on the Internet, the Atos Origin group liability cannot be
triggered for the message content. Although the sender endeavours to maintain
a computer virus-free network, the sender does not warrant that this
transmission is virus-free and will not be liable for any damages resulting
from any virus transmitted. 

View raw message