Zongle Wang
Zongle Wang
The failed tests from https://github.com/Kotlin/binary-compatibility-validator/pull/262#issuecomment-2247592185, they ref to the `settings.gradle.kts` already declare `rootProject`. See https://github.com/Kotlin/binary-compatibility-validator/blob/18cd0df801cde896675b0a4b6fdf082e3eef33f7/src/functionalTest/resources/examples/gradle/settings/settings-name-testproject.gradle.kts#L1
This happends due to running `./gradlew apiDump` in IDEA, as the test projects are enabled in IDEA env https://github.com/cashapp/paparazzi/blob/d2da4fd1854b8c66b02afcfc8b6bb8d6b4be558a/settings.gradle#L37-L40 The test projects are disabled on CI, so `apiCheck` tasks never...
After switching to `ubuntu-latest`, it works. Thanks for the help! BTW, the action worked on `ubuntu-24.04-arm` but failed randomly. I filed issue #141. Now it always fails on the arm...
Unrelated failure. https://github.com/tylerbwong/metalava-gradle/actions/runs/14280014407/job/40028511232?pr=132
Outdated.
Try things like ```groovy tasks.named('shadowJar') { from tasks.named('someTask').output } ```
Sounds good!
Inverted for https://github.com/willowtreeapps/assertk/blob/a69843f4452d2cf83bb6a787b138f8d90cfc3f90/assertk/src/commonMain/kotlin/assertk/assertions/map.kt#L118-L124
应该是和深度睡眠有关系，FCM 的延迟同理