-
Notifications
You must be signed in to change notification settings - Fork 643
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Launching coroutine in test lambda does not attach to the correct scope #830
Comments
This seem critical.
I think the reason is tge same as before failing. I'll look into it.
We should release a fix ASAP
…On Thu., Jun. 13, 2019, 16:45 Stephen Samuel, ***@***.***> wrote:
Seems like its not handled so the test doesn't complete properly.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#830>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAMBCI7OAFJE7SZFXGMNQZDP2KPVVANCNFSM4HX5V5JQ>
.
|
Agreed.
I've commented on your other fix, so once that's addressed and this, lets
release 3.3.3
On Thu, 13 Jun 2019 at 14:50, Leonardo Colman Lopes <
notifications@github.com> wrote:
… This seem critical.
I think the reason is tge same as before failing. I'll look into it.
We should release a fix ASAP
On Thu., Jun. 13, 2019, 16:45 Stephen Samuel, ***@***.***>
wrote:
> Seems like its not handled so the test doesn't complete properly.
>
> —
> You are receiving this because you are subscribed to this thread.
> Reply to this email directly, view it on GitHub
> <
#830
>,
> or mute the thread
> <
https://github.com/notifications/unsubscribe-auth/AAMBCI7OAFJE7SZFXGMNQZDP2KPVVANCNFSM4HX5V5JQ
>
> .
>
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#830>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAFVSGVA7O6E4BBXLBJLURLP2KQJDANCNFSM4HX5V5JQ>
.
|
Ok so this only happens if you're using the intellij kotlintest plugin.
If you're using the junit one it's fine.
…On Thu, 13 Jun 2019 at 14:51, Stephen Samuel (Sam) ***@***.***> wrote:
Agreed.
I've commented on your other fix, so once that's addressed and this, lets
release 3.3.3
On Thu, 13 Jun 2019 at 14:50, Leonardo Colman Lopes <
***@***.***> wrote:
> This seem critical.
>
> I think the reason is tge same as before failing. I'll look into it.
>
> We should release a fix ASAP
>
> On Thu., Jun. 13, 2019, 16:45 Stephen Samuel, ***@***.***>
> wrote:
>
> > Seems like its not handled so the test doesn't complete properly.
> >
> > —
> > You are receiving this because you are subscribed to this thread.
> > Reply to this email directly, view it on GitHub
> > <
> #830
> >,
> > or mute the thread
> > <
> https://github.com/notifications/unsubscribe-auth/AAMBCI7OAFJE7SZFXGMNQZDP2KPVVANCNFSM4HX5V5JQ
> >
> > .
> >
>
> —
> You are receiving this because you authored the thread.
> Reply to this email directly, view it on GitHub
> <#830>,
> or mute the thread
> <https://github.com/notifications/unsubscribe-auth/AAFVSGVA7O6E4BBXLBJLURLP2KQJDANCNFSM4HX5V5JQ>
> .
>
|
Seems to fail for
The test should pick up failures in the nested coroutine. |
sksamuel
changed the title
Throwing error in coroutine does not fail test
Launching coroutine in test lambda does not attach to the correct scope
Jan 16, 2020
This is a wider bug in that any launched coroutines don't attach to the scope of the text executor. Fixed now in master. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Seems like its not handled so the test doesn't complete properly.
The text was updated successfully, but these errors were encountered: