Skip to content

ci: bump timeout to 45m, match flavored APK outputs - #47

Merged
Dvorinka merged 5 commits into
mainfrom
ci/timeout-and-apk-path
Nov 12, 2026
Merged

Dvorinka merged 5 commits into
mainfrom
ci/timeout-and-apk-path

Conversation

@Dvorinka

@Dvorinka Dvorinka commented Nov 9, 2026

Copy link
Copy Markdown
Owner

Summary

  • timeout-minutes: 30 → 45 — cold self-hosted runners were dying at the cap in the post-build cache step after Gradle had already succeeded; the run read as a CI failure when it was just slow.
  • apk/debug/*.apk → apk/*/debug/*.apk — flavors emit apk/github/debug/ and apk/play/debug/; the old glob silently uploaded nothing.

Test plan

  • next CI run completes post-build steps and the debug-apk artifact is non-empty

Generated with Devin

@vercel

vercel Bot commented Nov 9, 2026 •

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated
nothing-modes Ready Ready Preview Nov 10, 2026 9:31am UTC

@mira-tdvorak

mira-tdvorak Bot commented Nov 9, 2026 •

Copy link
Copy Markdown

Mira PR Walkthrough

This PR addresses two CI/build issues: increases the GitHub Actions timeout from 30 to 45 minutes to prevent false failures on cold self-hosted runners, and updates the APK artifact glob pattern to correctly capture flavored build outputs (github/play) instead of only the default debug folder.

4 files reviewed


Comment @mira-tdvorak help to get the list of available commands and usage tips.

Kern runs are failing fleet-wide on repo.maven.apache.org 429s
(nativeruntime-dist-compat for Robolectric unit tests). Google
hosts a full read-only mirror — trying it before central avoids the
rate limit without changing resolution semantics.

Release runs also die on 'Cannot convert "" to File' when
NOTHING_MODES_KEYSTORE arrives empty (kern GITHUB_ENV propagation);
empty now falls back to the debug key like a missing var.

Authored By: TDvorak <info@tdvorak.dev>

Co-Authored-By: Devin <158243242+devin-ai-integration[bot]@users.noreply.github.com>
The 429 fix holds — the daemon now dies mid-build, OOM-killed in the
job container: 4g daemon heap plus unbounded parallel compiles and
Robolectric test forks overcommit the cgroup limit. Cap workers at 3
and run the Kotlin compiler in-process (no separate Kotlin daemon) on
CI only; local builds are unaffected.

Authored By: TDvorak <info@tdvorak.dev>

Co-Authored-By: Devin <158243242+devin-ai-integration[bot]@users.noreply.github.com>
workers.max wasn't enough — the daemon still died at :app compile.
Kern job containers run with --memory 6g (KERN_JOB_MEMORY on the
fleet); a 4g-heap daemon plus metaspace, native dex and test forks
crosses that at peak. Budget the whole cgroup: 2.6g heap, 768m
metaspace, max 3 worker forks.

Authored By: TDvorak <info@tdvorak.dev>

Co-Authored-By: Devin <158243242+devin-ai-integration[bot]@users.noreply.github.com>
The OOM fix held — the daemon survived and unit tests finally ran,
only to fail inside MavenArtifactFetcher: Robolectric downloads
android-all at test time through its own HTTP client, which ignores
Gradle repository config and hits the same Central 429. Point the
fetcher at the Google mirror via robolectric.dependency.repo.url on
every Test task.

Authored By: TDvorak <info@tdvorak.dev>

Co-Authored-By: Devin <158243242+devin-ai-integration[bot]@users.noreply.github.com>
@Dvorinka
Dvorinka merged commit a329867 into main Nov 12, 2026
5 checks passed
@Dvorinka Dvorinka mentioned this pull request Nov 12, 2026
2 of 4 tasks

This branch was successfully deployed

1 active deployment
Preview — daf1e983 Deployed Nov 10, 2026 by vercel[bot]
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

Successfully merging this pull request may close these issues.

1 participant