PL
kotlin.IllegalStateException: There is no event loop. Use runBlocking { ... } to start one. Does anyone know where this error is coming from? I've got some coroutine code that works fine on the JVM, but on macosX64 I get this error.Size: a a a
2019 November 18
PL
This code is in a Test Class. It looks something like this:
@Test
fun testCancelNullTask() = runBlocking(Dispatchers.Default) {
val task = Task.createNullTask()
delay(100)
task.cancel()
assertNull(task.result)
assertFalse(task.cancelled)
}
@Test
fun testCancelNullTask() = runBlocking(Dispatchers.Default) {
val task = Task.createNullTask()
delay(100)
task.cancel()
assertNull(task.result)
assertFalse(task.cancelled)
}
PL
All the tests fail with the same message
IS
Есть ли какие-нибудь варианты параметризированного тестирования на котлине?
Что-то вроде Spock для Kotlin
Что-то вроде Spock для Kotlin
AM
kotlin.IllegalStateException: There is no event loop. Use runBlocking { ... } to start one. Does anyone know where this error is coming from? I've got some coroutine code that works fine on the JVM, but on macosX64 I get this error.Generally speaking, threading is quite different on K/JVM and K/N. R
Current release version of kotlinx.coroutines doesn't support multithreading for K/N at all, but this is soon to be changed. Still, K/N adds limitations to what you can do, so I'd suggest reading through the docs.
https://kotlinlang.org/docs/reference/native/concurrency.html
Here's how it would work when kotlinx.coroutines is released (no ETA yet): https://github.com/Kotlin/kotlinx.coroutines/blob/native-mt/kotlin-native-sharing.md
Current release version of kotlinx.coroutines doesn't support multithreading for K/N at all, but this is soon to be changed. Still, K/N adds limitations to what you can do, so I'd suggest reading through the docs.
https://kotlinlang.org/docs/reference/native/concurrency.html
Here's how it would work when kotlinx.coroutines is released (no ETA yet): https://github.com/Kotlin/kotlinx.coroutines/blob/native-mt/kotlin-native-sharing.md
VP
Есть ли какие-нибудь варианты параметризированного тестирования на котлине?
Что-то вроде Spock для Kotlin
Что-то вроде Spock для Kotlin
Есть Spek
PL
Generally speaking, threading is quite different on K/JVM and K/N. R
Current release version of kotlinx.coroutines doesn't support multithreading for K/N at all, but this is soon to be changed. Still, K/N adds limitations to what you can do, so I'd suggest reading through the docs.
https://kotlinlang.org/docs/reference/native/concurrency.html
Here's how it would work when kotlinx.coroutines is released (no ETA yet): https://github.com/Kotlin/kotlinx.coroutines/blob/native-mt/kotlin-native-sharing.md
Current release version of kotlinx.coroutines doesn't support multithreading for K/N at all, but this is soon to be changed. Still, K/N adds limitations to what you can do, so I'd suggest reading through the docs.
https://kotlinlang.org/docs/reference/native/concurrency.html
Here's how it would work when kotlinx.coroutines is released (no ETA yet): https://github.com/Kotlin/kotlinx.coroutines/blob/native-mt/kotlin-native-sharing.md
Thanks I will have a look
AM
Thanks I will have a look
If your test don't involve any multithreading, just asynchrony, try to go for
runBlocking without parameter. That's also just a wild guess as I didn't touch K/N for a long time unfortunately.RI
Есть ли какие-нибудь варианты параметризированного тестирования на котлине?
Что-то вроде Spock для Kotlin
Что-то вроде Spock для Kotlin
я просто вот так использую, но можно поверх pair, triple, etc накрутить покрасивее синтаксис
IS
PL
If your test don't involve any multithreading, just asynchrony, try to go for
runBlocking without parameter. That's also just a wild guess as I didn't touch K/N for a long time unfortunately.Well at least now I get different errors 🤷♂️
AM
Well at least now I get different errors 🤷♂️
I'm hoping they are looking more actionable :)
PL
I'm hoping they are looking more actionable :)
Now I've got some weird gradle errors
PL
No clue what gradle wants from me haha
LS
it seems that the test process quit unexpectedly. run
test.kexe from build folder manually, likely it will segfaultLS
and report another issue to tracker, please 🙂
PL
and report another issue to tracker, please 🙂
Sure 😊