-
Notifications
You must be signed in to change notification settings - Fork 686
Closed
Description
Which version of Kotest are you using
6.0.0.M8
Description of the bug
I'm not sure if this is the only task that can fail like, but Gradle 9.0.0 doesn't allow accessing the project at runtime, and ultimately causes the jsNodeKotest
task to fail. I looked at the source code, and I'm pretty sure that in this instance, the failure is linked to the testModuleName
value in the task's source code. Even the println
stops at that point during the build.
println("specs: ${specs.getOrElse("")}")
println("Node executable ${nodeExecutable.get()}")
// the kotlin js compiler uses projectname-test as the module name, eg in build/js/packages
val testModuleName = "${project.name}-test"
println("JS Test Module $testModuleName")
Tasks of type jsNodeKotest result in FAILED with the following output:
- Task `:os-auto-updates-microservice:jsNodeKotest` of type `io.kotest.framework.gradle.tasks.KotestJsTask`: invocation of 'Task.project' at execution time is unsupported.
See https://docs.gradle.org/8.14.3/userguide/configuration_cache.html#config_cache:requirements:use_project_during_execution
- Task `:os-auto-updates-testing:jsNodeKotest` of type `io.kotest.framework.gradle.tasks.KotestJsTask`: invocation of 'Task.project' at execution time is unsupported.
See https://docs.gradle.org/8.14.3/userguide/configuration_cache.html#config_cache:requirements:use_project_during_execution
Regards.
Metadata
Metadata
Assignees
Labels
No labels