mirror of
https://github.com/fromchat-messenger/app.git
synced 2026-11-16 02:44:54 +03:00
f98f0c217b
Neither is related to the jmods work; both were visible only on the windows-11-arm runner. 1. Gradle hung at build shutdown. The runner's ambient JAVA_HOME is Temurin 21.0.12 aarch64, and JDK-8371740 — a LinkedTransferQueue race fixed only in JDK 26 — makes Gradle on Windows ARM64 hang whenever it runs on JDK 21+, failing the build after the installer was already written with "Timeout waiting for concurrent jobs to complete". Gradle's own repo and linroid/Ketch both carry workarounds for this. Pin the Gradle JVM to 17, which is what the x64 job already does; Adoptium ships no Windows aarch64 17, hence the new `java-distribution` input and zulu there. Packaging is unaffected: resolvePackagingJdkHome() rejects 17 as too old and falls back to the Java 25 toolchain JDK for jpackage. 2. "Ensure ARM64 packaging JDK" stalled for minutes and looked hung. The script only scanned C:\Program Files\Eclipse Adoptium, but hosted ARM64 runners ship their ARM64 Temurin 21 under the hostedtoolcache, so the scan missed it and fell through to downloading a ~180 MB JDK via Invoke-WebRequest + Expand-Archive. Re-running the job showed it still installing 3m24s later. Accept JAVA_HOME when it reports os.arch=aarch64 — the script's own comments already call Java 21 good enough as the Gradle daemon JVM.
f98f0c217b
·
2026-10-16 20:12:16 +03:00
History