Repository navigation
Improve error reporting for dumpsys meminfo - #187254
Conversation
…nfo parsing in devicelab
…en dumpsys meminfo fails to parse Changes assert to controlled DeviceException throw inside AndroidDevice.getMemoryStats when dumpsys meminfo parsing fails, providing descriptive diagnostics in production. Adds adb_test.dart test coverage. TAG=agy CONV=c27e0d56-32a6-48b9-9054-daf87ae39aa1
There was a problem hiding this comment.
Code Review
This pull request replaces an assertion with an explicit DeviceException when parsing dumpsys meminfo output fails in AndroidDevice.getMemoryStats, adds a corresponding unit test, and reformats a JSON decoding statement in IosDeviceDiscovery.discoverDevices. Feedback on the changes suggests simplifying the new unit test by removing the unnecessary async keyword and closure wrapper, allowing expect to handle the returned Future directly.
Co-authored-by: gemini-code-assist[bot] <176961590+gemini-code-assist[bot]@users.noreply.github.com>
jesswrd
left a comment
There was a problem hiding this comment.
Please add a unit test for the "happy" path which is when dumpsys meminfo is successfully parsed.
Also, consider updating the PR description from "Fixes #74085" to "Partially Addresses #74085." I think this PR addresses the issue but does not fix it. I think this PR helps us better diagnose the flake but doesn't actually fix the flake.
|
Done. Added a happy path unit test for |
|
autosubmit label was removed for flutter/flutter/187254, because The base commit of the PR is older than 7 days and can not be merged. Please merge the latest changes from the main into this branch and resubmit the PR. |
Improve error reporting for dumpsys meminfo parsing in devicelab
Partially Addresses #74085
Pre-launch Checklist
///).