Build failed in Jenkins: JMeter-trunk #2636

2012-10-11 Thread Apache Jenkins Server
See Changes: [sebb] Clarify -- [...truncated 614 lines...] [jar] Building jar: package: check-anakia: report-old-veloc

buildbot success in ASF Buildbot on jmeter-trunk

2012-10-11 Thread buildbot
The Buildbot has detected a restored build on builder jmeter-trunk while building ASF Buildbot. Full details are available at: http://ci.apache.org/builders/jmeter-trunk/builds/1274 Buildbot URL: http://ci.apache.org/ Buildslave for this Build: hemera_ubuntu Build Reason: scheduler Build Sourc

Re: Testing for nullity in IfController

2012-10-11 Thread sebb
On 11 October 2012 21:18, Philippe Mouawad wrote: > Hello, > I was wondering if there isn't a better way to do this, which I don't like > very much. It's not really testing for null, it's testing whether the variable is defined or not. One could use vars.get("myVar") == null in one of the script

Build failed in Jenkins: JMeter-trunk #2635

2012-10-11 Thread Apache Jenkins Server
See Changes: [pmouawad] Document the way to test for nullity in an IfController -- [...truncated 621 lines...] [jar] Building jar:

buildbot failure in ASF Buildbot on jmeter-trunk

2012-10-11 Thread buildbot
The Buildbot has detected a new failure on builder jmeter-trunk while building ASF Buildbot. Full details are available at: http://ci.apache.org/builders/jmeter-trunk/builds/1273 Buildbot URL: http://ci.apache.org/ Buildslave for this Build: hemera_ubuntu Build Reason: scheduler Build Source S

Testing for nullity in IfController

2012-10-11 Thread Philippe Mouawad
Hello, I was wondering if there isn't a better way to do this, which I don't like very much. Regards Philippe On Thu, Oct 11, 2012 at 10:15 PM, wrote: > Author: pmouawad > Date: Thu Oct 11 20:15:36 2012 > New Revision: 1397277 > > URL: http://svn.apache.org/viewvc?rev=1397277&view=rev > Log: > D

Build failed in Jenkins: JMeter-trunk #2634

2012-10-11 Thread Apache Jenkins Server
See -- [...truncated 614 lines...] [jar] Building jar: package: check-anakia: report-old-velocity: report-anakia-missing: ini

Re: Creating a Shared context between threads

2012-10-11 Thread Shmuel Krakower
Hmm I guess you are right. Just a suggestion. I didnt like this either but you guys are the one who develop JMeter, I am usually just working my way around until a feature or a bug gets developed, as I don't count on my coding skills to make it into the clean JMeter code. And I'm also too lazy..

Re: Creating a Shared context between threads

2012-10-11 Thread sebb
On 11 October 2012 08:00, Shmuel Krakower wrote: > How about the existing bsh.shared name space? I use it like this to even > share objects between thread groups in beanshell: > > MyClass UI = new MyClass(); > // Saving object to allow using it later for cleanup in tearDown phase. > bsh.shared.UI

Re: Creating a Shared context between threads

2012-10-11 Thread Shmuel Krakower
How about the existing bsh.shared name space? I use it like this to even share objects between thread groups in beanshell: MyClass UI = new MyClass(); // Saving object to allow using it later for cleanup in tearDown phase. bsh.shared.UI = UI; Best, Shmuel. On Wed, Oct 10, 2012 at 11:57 PM, Phil