Status Update
Comments
sy...@google.com <sy...@google.com> #2
Project: platform/frameworks/support
Branch: androidx-main
Author: Radha Nakade <
Link:
Migrate traffic from pixel2 to mediumphone on FTL emulators.
Expand for full commit details
Migrate traffic from pixel2 to mediumphone on FTL emulators.
Bug: 396715333
Test: ./gradlew emoji2:emoji2-emojipicker:ftlmediumphoneapi33
Change-Id: If5555443ca1a91479128e1bd6f4f909154c40ba2
Files:
- M
buildSrc/private/src/main/kotlin/androidx/build/FtlRunner.kt
Hash: c76f8094154101867327912e659ae47509755957
Date: Wed Feb 26 11:27:46 2025
sy...@google.com <sy...@google.com> #4
Hmm I think it didn't help the bots still seem flaky
sy...@google.com <sy...@google.com> #5
Bots running with chromium builds seem not flaky at all:
I wonder why do these tests even run on Chrome builds since if internal regex patters are enabled they should instantly success.
sy...@google.com <sy...@google.com> #6
It seems that the bots from the "Chrome" builders that are flaky are not specifying gn args marking the build as branded. There are bots in the "Chrome" builders that specify gn args for branding them explicitly, and they seem ok.
Unofficial builds on their own are fine (what we can verify by looking at the "Chromium" builders. I wonder whether the issue lies in autofill logic or bots configuration.
Description
Both tests are regularly crashing on iOS device bot (ipad-device/iphone-device), which may be causing the unittest job to fail on those bots as well.
The issue started around end of Febuary 2025 and the exception looks similar tohttps://crbug.com/383523218