=tck #153 spec317 test must explicitly check the error was asserted on

Fixes the `spec317_mustSignalOnErrorWhenPendingAboveLongMaxValue` which was added for `1.0.0.M1` to explicitly check for triggering the overflow onError signal as well as giving more breathing room to the implementations (avoid escaping the loop and even the entire test before the onError triggers).

Resolves https://github.com/reactive-streams/reactive-streams/pull/154
On Mon, Nov 24, 2014 at 5:49 PM, Konrad Malawski <notifications@github.com>
wrote:

> In tck/src/main/java/org/reactivestreams/tck/PublisherVerification.java:
>
> > @@ -793,7 +794,9 @@ public void spec317_mustSignalOnErrorWhenPendingAboveLongMaxValue() throws Throw
> >            sub.request(Long.MAX_VALUE - 1);
> >
> >            try {
> > +            Thread.sleep(SPIN_ASSERT_DELAY);
>
> The thread running the test :)
>
If it's the test-runner thread and it does not impact the publisher or
subscriber, I'm not that worried about it.



> —
> Reply to this email directly or view it on GitHub
> <https://github.com/reactive-streams/reactive-streams/pull/154/files#r20802911>
> .
>



-- 
Cheers,
√