Scott Pierce

This is the github action that's running it. It's building it for multiple cpu archs. ``` build-docker: name: Build Docker runs-on: [ self-hosted, docker ] container: image: scottpierce/docker:latest env: IMAGE_DOCKER:...

``` env: PLATFORMS: linux/amd64,linux/arm64 PLATFORM_AMD64: linux/amd64 ```

I'm seeing a similar problem with multiplatform. The work around was: ```Kotlin sourceSets { getByName("androidMain") { kotlin.srcDir("build/generated/moko/androidMain/src") } } ```

> Thank for the solution this have solve my problems too :) ✅ > > I think we can close this ticket ❌ I don't think so. This should be...

Any news on this? @mg6maciej

@mg6maciej Are there any plans to fix this in the near future? Being able to compile with Java 8 is starting to become a necessity for my team.

So because of this issue, we migrated off of hrisey a few months back. A few things happened as a result: 1. Our build times dropped 2. A memory leak...

I'm also wondering about this as well.

I've seen this happen again. This might be the initial error: ``` Error: Cache upload failed because file read failed with EBADF: bad file descriptor, read ```

I've also noticed this is extremely reproducible for some reason. This failure happens a lot for my docker runners when things are in parallel, especially now that I have 8...