Setup and TearDown executed by different threads

[vyazelenko at yahoo.com]

Ok, I'm said panda now. ;( I'll have to workaround the issue on my side. Most likely by dropping @TearDowns and moving all logic into @Setups...

P.S. Thanks for JavaDoc update and 0.9.7 release! :)

Best regards,
Dmitry

Sent from my iPhone

> On Aug 15, 2014, at 15:59, Aleksey Shipilev <aleksey.shipilev at oracle.com> wrote:
> 
>> On 08/13/2014 06:54 PM, Aleksey Shipilev wrote:
>> Let me see how messy it would be to track the @Setup/@TearDown callers.
> 
> Okay, it seems messier than I expected at the first glance. There are
> multiple things to consider when tracking the @State owner:
> - do we share the owner across multiple Levels?
> - what do we do if the owner exits abruptly?
> - how do we handle the absence of paired @Setup/@TearDowns?
> - ...?
> 
> Not that isn't not doable, but the change seems too intrusive to do in a
> Release Candidate. It also intersects with Chris Vest's example of
> benchmark being stuck if one of the threads in asymmetric benchmarks
> throws the exception. Let us consider this for post 1.0 revisions.
> 
> I had updated the @Setup/@TearDown Javadocs to (un)specify which thread
> is going to call the fixture methods though.
> 
> Thanks,
> -Aleksey.
>