Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Could not find "org.jetbrains.kotlin:kotlinx-atomicfu-runtime" #288

Closed
JavierSegoviaCordoba opened this issue May 28, 2022 · 6 comments
Closed

Comments

@JavierSegoviaCordoba
Copy link

I can't reproduce it locally.

> Task :semver-core:compileTestKotlinJsIr FAILED
e: Could not find "org.jetbrains.kotlin:kotlinx-atomicfu-runtime" in [/home/runner/.kotlin/daemon]
e: java.lang.IllegalStateException: FATAL ERROR: Could not find "org.jetbrains.kotlin:kotlinx-atomicfu-runtime" in [/home/runner/.kotlin/daemon]

Run: https://github.com/JavierSegoviaCordoba/semantic-versioning-kmp/runs/6636861234?check_suite_focus=true

@bigdaz
Copy link
Member

bigdaz commented Jun 3, 2022

I'm not sure the gradle-build-action is at fault here. In the failing build, the Gradle User Home directory was not restored from cache, but it looks like some restored state is referencing a file in /home/runner/.kotlin/daemon.
The only idea I have would be that this is caused by restoring the .konan directory from cache.

  • Is this issue reproducible in your workflow?
  • Does removing the .konan cache step resolve it?

@JavierSegoviaCordoba
Copy link
Author

Before reporting I tried to remove those cache directories but the problem persisted.

But locally I can't reproduce it.

I tried to change the jdk distribution and I got the same issue in actions.

@bigdaz
Copy link
Member

bigdaz commented Jun 3, 2022

A few things that might help you narrow down what's causing this:

  • Try building with gradle-build-action@main and use the new Job Summary to determine which Gradle User Home cache entries are being restored (and which aren't)
  • Locally, try selectively deleting the parts of Gradle User Home that are not restored (ie remove files matching /home/runner/.gradle/caches/*/kotlin-dsl/*/*). This will allow you to emulate locally what a partial Gradle User Home restore would do.

@bigdaz
Copy link
Member

bigdaz commented Jun 3, 2022

Oh, and check if the issue persists when you disable the Gradle User Home cache: https://github.com/gradle/gradle-build-action#caching

@JavierSegoviaCordoba
Copy link
Author

Looks like someone has been able to reproduce locally and a fix from coroutines is coming soon.

Kotlin/kotlinx.coroutines#3305

Really thank you for your help and sorry for this unnecessary report :/

Anyway I have noted the tips for future issues 😃

@bigdaz
Copy link
Member

bigdaz commented Jun 4, 2022

Glad you got it sorted out. Thanks for continuing to provide feedback!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants