Merged,
Maxim.
On 04/15/16 18:25, Bill Fischofer wrote:
On Tue, Feb 16, 2016 at 8:02 AM, Ivan Khoronzhuk
> wrote:
When test for single thread is finished the following test for
many threads can be started, and for some
On Tue, Feb 16, 2016 at 8:02 AM, Ivan Khoronzhuk wrote:
> When test for single thread is finished the following test for
> many threads can be started, and for some implementations can
> happen that future one event can arrive to main thread, as it was
> requested in
It's on my list. :) I should get to it today.
On Fri, Apr 15, 2016 at 7:51 AM, Ivan Khoronzhuk wrote:
> Hi Bill,
>
> What about to review this one?
>
> On 16.02.16 16:02, Ivan Khoronzhuk wrote:
>
>> When test for single thread is finished the following test for
>>
Hi Bill,
What about to review this one?
On 16.02.16 16:02, Ivan Khoronzhuk wrote:
When test for single thread is finished the following test for
many threads can be started, and for some implementations can
happen that future one event can arrive to main thread, as it was
requested in previous
ping
On 18.02.16 17:56, Ivan Khoronzhuk wrote:
ping
On 16.02.16 16:02, Ivan Khoronzhuk wrote:
When test for single thread is finished the following test for
many threads can be started, and for some implementations can
happen that future one event can arrive to main thread, as it was
ping
On 16.02.16 16:02, Ivan Khoronzhuk wrote:
When test for single thread is finished the following test for
many threads can be started, and for some implementations can
happen that future one event can arrive to main thread, as it was
requested in previous test. As result one event can be
When test for single thread is finished the following test for
many threads can be started, and for some implementations can
happen that future one event can arrive to main thread, as it was
requested in previous test. As result one event can be lost for rest
threads. So, it's better to pause