Klib validation failing on CI but not locally

[JakeWharton]

* What went wrong:	
Execution failed for task ':redwood-layout-modifiers:klibApiMerge'.	
> java.io.FileNotFoundException: File does not exist: /Users/runner/work/redwood/redwood/redwood-layout-modifiers/build/api/js/redwood-layout-modifiers.klib.api	

• Project: https://github.com/cashapp/redwood
• PR: Enable klib ABI dump cashapp/redwood#1884
• SHA: 5dc8c3377b3c3b7760416dcc5308033090213ca3

Attempt 1

• Action log: https://github.com/cashapp/redwood/actions/runs/8360157932/job/22885183135?pr=1884
• Build scan: https://gradle.com/s/p5ha2lzccuwiq

Attempt 2

• Action log: https://github.com/cashapp/redwood/actions/runs/8360157932/job/22891922690?pr=1884
• Build scan: https://gradle.com/s/ehehhmdxrrf5a

Attempt 3

• Action log: https://github.com/cashapp/redwood/actions/runs/8360157932/job/22893510501?pr=1884
• Build scan: https://gradle.com/s/tiijq75sgyt4c

I have not been able to reproduce this locally on my Mac. I tried executing the same command (after a clean) with --max-workers=3 to match the core count of the CI machine but it always succeeds (5 attempts).

I also don't know why it's always this specific module and the JS target that fails. I apply it to ~40 modules in this build, most of which are multiplatform containing JS targets. Very weird.

It's possible the problem can be identified just from looking at the code of the plugin, but I don't have time to do that right now. I can try investigating more later tonight or tomorrow, but figured I'd file the issue first.

[fzhinkin]

@JakeWharton thanks for reporting!

[fzhinkin]

There's nothing specific about JS target in this particular case, it just appears to be the first target to load a dump for merging.
For API build tasks, we're skipping a task if there are no sources associated with it (and :redwood-layout-modifiers is indeed "empty"), but all other tasks are not skipped and thus fail.

[JakeWharton]

That module contains only generated sources, which are correctly picked up by the dump: https://github.com/cashapp/redwood/pull/1884/files#diff-01c56a8c31dca2ba8b0d2218624f995999da354e5ac75bc91877b5dbb6abd60c

The sources are produced by adding a Task to the source set here: https://github.com/cashapp/redwood/blob/0b99e1067cc61ee58b3560ac949bb83cba3bb506/redwood-gradle-plugin/src/main/kotlin/app/cash/redwood/gradle/RedwoodGeneratorPlugin.kt#L106-L107. Adding the task directly means Gradle will automatically run the task before anyone can consume the source set. The task's @OutputDirectory has the files which are then included in the source set.

[JakeWharton]

I tried adding the task to the source set as soon as possible (when the multiplatform plugin is applied), but it didn't change the outcome.

[lukellmann]

I get a similar exception on Windows for this project when klib validation is enabled here (by adding klib.enabled = true):

> Task :core:live-tests:klibApiMergeInferred FAILED                                                                                                                                                                                                                                                                           

FAILURE: Build failed with an exception.                                                                                                                                                                                                                                                                                      

* What went wrong:
Execution failed for task ':core:live-tests:klibApiMergeInferred'.
> java.io.FileNotFoundException: File does not exist: C:\...\kord\core\live-tests\build\api\js\live-tests.klib.api 

The relevant parts of the project layout look like this:

kord (root project, BCV plugin not applied)
|
+-- core (public api subproject, BCV plugin applied)
    |
    +-- live-tests (internal subproject, BCV plugin not applied)

It seems like BCV tries to find the .klib.api file for a subproject that won't ever create one because the BCV plugin isn't applied there.

The workaround I found is putting this into kord/core/build.gradle.kts:

apiValidation {
    ignoredProjects += "live-tests"
}