You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We'd need them in all the pools till we roll staging into prod.
According to the original bug:
gen_snapshot compiles and links on ARM64 Linux
CI builder produces linux-arm64.zip archives for all Android target CPUs (arm, arm64, x64, riscv64) in both profile and release modes
analyze_snapshot produces analyze-snapshot-linux-arm64.zip for 64-bit targets
Looking at the android aot build, this needs ~8 per build in the MQ, 3 builds in the MQ right now so 24. We could bump that to 50 just to be safe (5 builds and something running tests in post).
FYI for this issue's scope: the reland of #182552 (AOT engine for Android arm64 targets) no longer depends on this bot pool. The reland builder cross-compiles gen_snapshot from the existing linux-x64 pool — empirically validated on native x86_64 hardware on 2026-05-29 against c7f49fe0 (producing the linux-arm64.zip artifact) and re-validated 2026-06-04 against 14c05c42 (then-current main).
That means the missing flutter/android/sdk/all/linux-arm64 CIPD platform isn't a blocker for the AOT engine reland either (gclient runs on x64, the SDK download condition is unchanged).
This issue is still useful for the broader linux-arm64-as-Flutter-host story — Android emulator builder (where the original staging bot failure happened), arm64 host tooling, and any future native arm64 builds — but it isn't on the critical path for relanding #182552.
This issue is marked P1 but has had no recent status updates.
The P1 label indicates high-priority issues that are at the top of the work list. This is the highest priority level a bug can have if it isn't affecting a top-tier customer or breaking the build. Bugs marked P1 are generally actively being worked on unless the assignee is dealing with a P0 bug (or another P1 bug). Issues at this level should be resolved in a matter of months and should have monthly updates on GitHub.
Please consider where this bug really falls in our current priorities, and label it or assign it accordingly. This allows people to have a clearer picture of what work is actually planned. Thanks!
Activity
jtmcdole commentedon May 18, 2026
@ievdokdm - do you think you could look at this while we've been updating machines?
ievdokdm commentedon May 19, 2026
@jtmcdole in which pools ( staging / try / prod ) and how many instances we want to have ?
ievdokdm commentedon May 19, 2026
added test
linux-arm64to staging pool:Config: https://chrome-internal-review.git.corp.google.com/c/infradata/config/+/9311600
Swarming Bot Page: https://chromium-swarm.appspot.com/bot?id=flutter-staging-prj-arm64-ubuntu-us-central1-a-0-zbmf
ievdokdm commentedon May 19, 2026
https://luci-milo.appspot.com/ui/p/flutter/builders/staging/Linux_android_emu%20external_textures_integration_test/17135/overview
failed to execute on this bot. @jtmcdole say that https://g3doc.corp.google.com/company/teams/flutter/infrastructure/luci/cipd.md?cl=head should be added to
https://chrome-infra-packages.appspot.com/p/flutter/android/sdk/all
jtmcdole commentedon May 20, 2026
We'd need them in all the pools till we roll staging into prod.
According to the original bug:
Looking at the android aot build, this needs ~8 per build in the MQ, 3 builds in the MQ right now so 24. We could bump that to 50 just to be safe (5 builds and something running tests in post).
Add a tag to the Linux platform properties in .ci.yaml that specifies…
Add a tag to the Linux platform properties in .ci.yaml that specifies…
dbebawy commentedon Jun 5, 2026
Reland PR is open: #187591.
FYI for this issue's scope: the reland of #182552 (AOT engine for Android arm64 targets) no longer depends on this bot pool. The reland builder cross-compiles
gen_snapshotfrom the existing linux-x64 pool — empirically validated on native x86_64 hardware on 2026-05-29 againstc7f49fe0(producing thelinux-arm64.zipartifact) and re-validated 2026-06-04 against14c05c42(then-currentmain).That means the missing
flutter/android/sdk/all/linux-arm64CIPD platform isn't a blocker for the AOT engine reland either (gclient runs on x64, the SDK download condition is unchanged).This issue is still useful for the broader linux-arm64-as-Flutter-host story — Android emulator builder (where the original staging bot failure happened), arm64 host tooling, and any future native arm64 builds — but it isn't on the critical path for relanding #182552.
Add a tag to the Linux platform properties in .ci.yaml that specifies…
flutter-triage-bot commentedon Sep 23, 2026
This issue is marked P1 but has had no recent status updates.
The P1 label indicates high-priority issues that are at the top of the work list. This is the highest priority level a bug can have if it isn't affecting a top-tier customer or breaking the build. Bugs marked P1 are generally actively being worked on unless the assignee is dealing with a P0 bug (or another P1 bug). Issues at this level should be resolved in a matter of months and should have monthly updates on GitHub.
Please consider where this bug really falls in our current priorities, and label it or assign it accordingly. This allows people to have a clearer picture of what work is actually planned. Thanks!