happy hakking!
On Tue, Jun 20, 2017 at 10:32 PM, Sean Shubin wrote:
> Regarding #1, that is the information I was missing, thank you for
> clearing that up. Hopefully that will guide me to how to test asynchronous
> code with an synchronous execution context.
>
> Regarding #2 and #3, I agree, I
Regarding #1, that is the information I was missing, thank you for clearing
that up. Hopefully that will guide me to how to test asynchronous code
with an synchronous execution context.
Regarding #2 and #3, I agree, I was just trying to figure out what was
going on. The reportFailure behavior
Hi Sean,
On Tue, Jun 20, 2017 at 12:51 AM, Sean Shubin wrote:
> While I was trying to stub out an execution context to test concurrent
> code, I noticed some surprising behavior demonstrated below. I would have
> expected the exception thrown by the Future to cause reportFailure to be
> invoked
While I was trying to stub out an execution context to test concurrent
code, I noticed some surprising behavior demonstrated below. I would have
expected the exception thrown by the Future to cause reportFailure to be
invoked. To my surprise, reportFailure never got called at all, and the
run
