GitHub user benbenw opened a pull request:

    https://github.com/apache/jmeter/pull/141

    Bug 59067 JMeter fail to iterate over SimpleController after an assertion 
error.

    Please review carefully as it may break the world...
    
    The controller does not restart at the first sampler
    The pb is that in JMeterThread#triggerEndOfLoopOnParentControllers the
    Sampler used is not always the "real" one, but it can be a
    TransactionSampler, if there are some other controllers
    (Simplecontroller) between this TransactionSampler and the http sampler,
    triggerEndOfLoop will not be called for those controllers.
    
    the idea behind the patch is to always do the tree traversal from the
    real sampler.

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/benbenw/jmeter endofloop

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/jmeter/pull/141.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #141
    
----
commit c866e4279031364f76e2f34cf3165253b1cdc9e5
Author: benoit <[email protected]>
Date:   2016-02-25T15:15:09Z

    Bug 59067 JMeter fail to iterate over SimpleController after an
    assertion error.
    The controller does not restart at the first sampler
    The pb is that in JMeterThread#triggerEndOfLoopOnParentControllers the
    Sampler used is not always the "real" one, but it can be a
    TransactionSampler, if there are some other controllers
    (Simplecontroller) between this TransactionSampler and the http sampler,
    triggerEndOfLoop will not be called for those controllers.
    
    the idea behind the patch is to always do the tree traversal from the
    real sampler.

----


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---

Reply via email to