I'm testing Kotlin 2.5.0-Beta1 with my JS/WasmJS p...
# eap
r
I'm testing Kotlin 2.5.0-Beta1 with my JS/WasmJS project. Upgrading Kotlin version and running old test configuration works fine. Moving JS tests to new Playwright-based DSL also works fine. But moving WasmJS tests to playwright ends with some gradle error. Stacktrace in thread.
👀 1
🍿 1
thank you color 1
Copy code
* What went wrong:
A problem was found with the configuration of task ':modules:kilua-rpc-javalin-koin:wasmJsTestBundleAsEsm' (type 'EsmBundleKotlinJsTests').
Input file does not exist
  In plugin 'org.jetbrains.kotlin.gradle.plugin.BuildMetricsPlugin_Decorated' type 'org.jetbrains.kotlin.gradle.targets.js.testing.EsmBundleKotlinJsTests' property 'kotlinLinkerOutputFiles' specifies directory '/home/rjaros/git/kilua-rpc/build/wasm/packages/kilua-rpc-modules-kilua-rpc-javalin-koin-test/kotlin' which doesn't exist
    An input file was expected to be present but it doesn't exist
    For more information, please refer to <https://docs.gradle.org/9.8.0/userguide/validation_problems.html#input_file_does_not_exist> in the Gradle documentation.
    Possible solutions:
      1. Make sure the directory exists before the task is called.
      2. Make sure that the task which produces the directory is declared as an input.

* Try:
> Run with --scan to get full insights from a Build Scan (powered by Develocity).

* Exception is:
org.gradle.internal.execution.WorkValidationException: A problem was found with the configuration of task ':modules:kilua-rpc-javalin-koin:wasmJsTestBundleAsEsm' (type 'EsmBundleKotlinJsTests').
        at org.gradle.internal.execution.WorkValidationException.withSummaryForContext(WorkValidationException.java:55)
        at org.gradle.internal.execution.impl.DefaultExecutionProblemHandler.throwValidationException(DefaultExecutionProblemHandler.java:70)
        at org.gradle.internal.execution.impl.DefaultExecutionProblemHandler.handleReportedProblems(DefaultExecutionProblemHandler.java:60)
        at org.gradle.internal.execution.steps.ValidateStep.execute(ValidateStep.java:97)
        at org.gradle.internal.execution.steps.ValidateStep$Mutable.execute(ValidateStep.java:65)
        at org.gradle.internal.execution.steps.CaptureMutableStateBeforeExecutionStep.executeMutable(CaptureMutableStateBeforeExecutionStep.java:86)
        at org.gradle.internal.execution.steps.CaptureMutableStateBeforeExecutionStep.execute(CaptureMutableStateBeforeExecutionStep.java:65)
        at org.gradle.internal.execution.steps.CaptureMutableStateBeforeExecutionStep.execute(CaptureMutableStateBeforeExecutionStep.java:45)
        at org.gradle.internal.execution.steps.SkipEmptyMutableWorkStep.executeWithNonEmptySources(SkipEmptyMutableWorkStep.java:210)
        at org.gradle.internal.execution.steps.SkipEmptyMutableWorkStep.executeMutable(SkipEmptyMutableWorkStep.java:85)
        at org.gradle.internal.execution.steps.SkipEmptyMutableWorkStep.executeMutable(SkipEmptyMutableWorkStep.java:53)
        at org.gradle.internal.execution.steps.MutableStep.execute(MutableStep.java:26)
        at org.gradle.internal.execution.steps.legacy.MarkSnapshottingInputsStartedStep.execute(MarkSnapshottingInputsStartedStep.
a
Thanks for reporting! Maybe you can have some reproducer as well?
Feels like the kotlin wasm link task wasnt executed or didnt provide the outputs that esm bunde task expects. In default project setup it works ok. So I wonder about your setup
r
I can make a branch of my project to reproduce
🔥 2
🙏 2
Checking out
new-test-dsl
and running
./gradlew allTest
should reproduce the error
thank you color 2
Should I fill an issue?
a
Yeah, it is always good idea to make it official.