[android] make failing to acquire a java image non-fatal.#56105
[android] make failing to acquire a java image non-fatal.#56105auto-submit[bot] merged 1 commit intoflutter:mainfrom
Conversation
|
It looks like this pull request may not have tests. Please make sure to add tests before merging. If you need an exemption, contact "@test-exemption-reviewer" in the #hackers channel in Discord (don't just cc them here, they won't see it!). If you are not sure if you need tests, consider this rule of thumb: the purpose of a test is to make sure someone doesn't accidentally revert the fix. Ask yourself, is there anything in your PR that you feel it is important we not accidentally revert back to how it was before your fix? Reviewers: Read the Tree Hygiene page and make sure this patch meets those guidelines before LGTMing. The test exemption team is a small volunteer group, so all reviewers should feel empowered to ask for tests, without delegating that responsibility entirely to the test exemption group. |
flutter/engine@48ff670...b8b28c8 2024-10-24 [email protected] [android] make failing to acquire a java image non-fatal. (flutter/engine#56105) 2024-10-24 [email protected] Roll Fuchsia Linux SDK from NxrFCTty8wV4-6Cpl... to Y4TdnTpLdkI107K42... (flutter/engine#56096) Also rolling transitive DEPS: fuchsia/sdk/core/linux-amd64 from NxrFCTty8wV4 to Y4TdnTpLdkI1 If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/flutter-engine-flutter-autoroll Please CC [email protected],[email protected] on the revert to ensure that a human is aware of the problem. To file a bug in Flutter: https://github.com/flutter/flutter/issues/new/choose To report a problem with the AutoRoller itself, please file a bug: https://issues.skia.org/issues/new?component=1389291&template=1850622 Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+doc/main/autoroll/README.md
…gine#56105) See failures in https://logs.chromium.org/logs/flutter/buildbucket/cr-buildbucket/8733165720607371809/+/u/step_is_flaky:_run_platform_views_scroll_perf__timeline_summary/stdout If we fail to acquire the next image from the image reader, its ok to return null from this method as the engine already handles displaying nothing. THe crashes are due to us ... choosing to crash, which isn't really meaningful.
See failures in https://logs.chromium.org/logs/flutter/buildbucket/cr-buildbucket/8733165720607371809/+/u/step_is_flaky:_run_platform_views_scroll_perf__timeline_summary/stdout
If we fail to acquire the next image from the image reader, its ok to return null from this method as the engine already handles displaying nothing.
THe crashes are due to us ... choosing to crash, which isn't really meaningful.