Skip to content

camera_android and camera_android_camerax integration tests failure on image resolution #154682

Closed
flutter/packages
#8193

Description

@yaakovschectman

Internal: b/376074365

The packages PR https://github.com/flutter/packages/pull/7587/checks which only updates the targeted SDK for example apps and makes some tweaks to the manifests as necessary to do so is resulting in instrumentation test failures (https://logs.chromium.org/logs/flutter/buildbucket/cr-buildbucket/8737614895298399505/+/u/Run_package_tests/Firebase_Test_Lab/stdout) for the camera_android and camera_android_camerax packages, either from timing out or from an image being taken at a higher than expected resolution.
Locally, running dart run script/tool/bin/flutter_plugin_tools.dart drive-examples --android --packages=camera_android_camerax,camera_android on the branch of that PR resulted in failed assertions for the image resolutions, as well. However, when checking out the main branch again, and running the above command on main, those tests continue to fail.

Activity

  1. yaakovschectman commented on Sep 5, 2024

    @yaakovschectman
    ContributorAuthor

    @camsim99 Do you have ideas on how I might confirm that the failures I see locally share their cause with whatever is going wrong for PR checks, or any other info regarding the cause of those failures?

  2. added
    in triagePresently being triaged by the triage team
    packageflutter/packages repository. See also p: labels.
    f: integration_testThe flutter/packages/integration_test plugin
    team-androidOwned by Android platform team
    platform-androidAndroid applications specifically
    and removed
    in triagePresently being triaged by the triage team
    on Sep 6, 2024
  3. camsim99 commented on Sep 6, 2024

    @camsim99
    Contributor

    @yaakovschectman Noting the actual image resolutions that the devices choose and causes the tests to fail may be useful. I don't know what device you're using locally (like if it's the same as those running in CI) but noting it will still be helpful to help determine if it's something with CameraX and how it behaves on certain devices or how we're using CameraX.

    I know this doesn't "confirm" exactly but if you're seeing it locally and in CI and it's clearly an issue with what resolution is being chosen, I think it's a safe assumption.

  4. yaakovschectman commented on Sep 6, 2024

    @yaakovschectman
    ContributorAuthor

    The logs from the firebase tests show it used a Pixel 7 API 33, and that it expected a resolution of 240 but got 1080. Locally running integration tests with main checked out with a matching emulator running still fails that same "Capture specific image resolutions" test, same as the firebase failure.

  5. added
    P2Important issues not at the top of the work list
    triaged-androidTriaged by Android platform team
    on Sep 12, 2024
  6. jesswrd commented on Nov 15, 2024

    @jesswrd
    Contributor
  7. self-assigned this
    on Nov 21, 2024
  8. github-actions commented on Dec 27, 2024

    @github-actions

    This thread has been automatically locked since there has not been any recent activity after it was closed. If you are still experiencing a similar issue, please open a new bug, including the output of flutter doctor -v and a minimal reproduction of the issue.

  9. locked as resolved and limited conversation to collaborators on Dec 27, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Labels

P2Important issues not at the top of the work listp: cameraThe camera pluginpackageflutter/packages repository. See also p: labels.platform-androidAndroid applications specificallyteam-androidOwned by Android platform teamtriaged-androidTriaged by Android platform team

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions