chore(ci): remove Cirrus runners and use only Bitrise - #6563
1 issue
code-review: Found 1 issue (1 medium)
Medium
Native test-android uses ubuntu-latest instead of stated ubuntu-24.04-16core - `.github/workflows/native-tests.yml:116`
Native test-android runs on ubuntu-latest instead of ubuntu-24.04-16core, which conflicts with the stated standardization requirements and may cause CI timeouts or OOM.
Also found at:
.github/workflows/e2e-v2.yml:61.github/workflows/e2e-v2.yml:250
⏱ 7m 33s · 254.6k in / 80.1k out · $0.40
Annotations
Check warning on line 116 in .github/workflows/native-tests.yml
sentry-warden / warden: code-review
Native test-android uses ubuntu-latest instead of stated ubuntu-24.04-16core
Native `test-android` runs on `ubuntu-latest` instead of `ubuntu-24.04-16core`, which conflicts with the stated standardization requirements and may cause CI timeouts or OOM.
Check warning on line 61 in .github/workflows/e2e-v2.yml
sentry-warden / warden: code-review
[5MW-EFJ] Native test-android uses ubuntu-latest instead of stated ubuntu-24.04-16core (additional location)
Native `test-android` runs on `ubuntu-latest` instead of `ubuntu-24.04-16core`, which conflicts with the stated standardization requirements and may cause CI timeouts or OOM.
Check warning on line 250 in .github/workflows/e2e-v2.yml
sentry-warden / warden: code-review
[5MW-EFJ] Native test-android uses ubuntu-latest instead of stated ubuntu-24.04-16core (additional location)
Native `test-android` runs on `ubuntu-latest` instead of `ubuntu-24.04-16core`, which conflicts with the stated standardization requirements and may cause CI timeouts or OOM.