CI: keep JVM crash logs and try C1-only JIT on the runner

Runs on the Gitea runner crash intermittently on three JDK vendors. Upload hs_err/replay logs on failure so the failing frame survives the job container, and drop C2 (TieredStopAtLevel=1) for the Gradle and Kotlin daemons to test whether the optimising JIT is the trigger. Co-Authored-By: Claude Sonnet 5.5 <[email protected]> Claude-Session: https://claude.ai/code/session_01YGRgChhwbwWr5yYrHTd9pL
2026-10-14 14:34:10 -06:00
parent 4ffe817d5f
commit 33a253d80c
2 changed files with 21 additions and 1 deletions
@@ -80,6 +80,19 @@ jobs:
          if-no-files-found: error
          retention-days: 14

+      - name: Upload JVM crash logs
+        # A JVM crash writes hs_err_pid*.log into the workspace, which dies
+        # with the job container; keep it so the failing frame can be read.
+        if: failure()
+        uses: actions/upload-artifact@v4
+        with:
+          name: ProLibertateGames-jvm-crash
+          path: |
+            hs_err_pid*.log
+            replay_pid*.log
+          if-no-files-found: ignore
+          retention-days: 14
+
      - name: Upload lint and test reports
        # Reports are most useful precisely when a step above failed.
        if: always()