DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://issues.apache.org/bugzilla/show_bug.cgi?id=41612>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=41612 ------- Additional Comments From [EMAIL PROTECTED] 2007-05-11 09:10 ------- (In reply to comment #1) > Created an attachment (id=20171) --> (http://issues.apache.org/bugzilla/attachment.cgi?id=20171&action=view) [edit] > Suggested patch > > The reason for the observed behaviour, is that currently, the condition on the > "if controller" is evaluated for each sample / loop iteration INSIDE the if > controller. > > I think that is incorrect. I think the "if controller" should only evaluate > its' condition when the "if block" is entered, and if the condition is > evaluated to true, then all the samplers and controllers inside the "if block" > should be executed. > > The suggested patch also contains a minor change to ThreadGroupGui, which sets > the name of the LoopController for the ThreadGroup, so that it is easier to > debug which controllers are executed. This change is not needed to fix this > bug, so if you do not like it, then just drop that part. After thinking about it a bit more, I think I need to test having an IF controller inside a Loop. I'm not sure that the current suggested patch, with the "isFirst()" test is correct. -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
