benny.huo
04/21/2019, 1:55 AMjoin
on an exceptionally completed job. After days digging, I figure out that if the join
call falls into the fast-path or successfully suspending, a CancellationException will be thrown in this case, but if the join
call falls into the joinSuspend
path but not successfully suspending, no CancellationException will happen. I just wonder that is it a bug to get inconsistent result from join
with the same code?
I have created a gist here https://gist.github.com/enbandari/0321cffa792e0f98d90e0e77682aeaed to make it more clear.bdawg.io
04/21/2019, 2:43 AMbenny.huo
04/21/2019, 3:06 AMelizarov
04/21/2019, 9:55 AMjoin
. Fixing it.benny.huo
04/21/2019, 10:26 AM