Skip to content

Unclear documentation on running a test on an emulator in flutter/engine #143374

@matanlurey

Description

@matanlurey

As-per @keyonghan, I tried to reference our Wiki when iterating on flutter/engine#50583 (in short, I want to run an existing test-script with Android emulator v28 instead of the usual v34). I wasn't able to find what I expected.

Here is what I tried referencing:

However, I'm not really sure if my current test cases (ci.yaml, ci/builders/linux_android_emulator.json run on the Devicelab? At the minimum the documentation seems different than what I see, leading me to believe the engine tests are not running on the Devicelab.

Wiki Instructions I read

image

I also checked the Flutter Self Service Index, but the section on Emulators support just points to the same page as above.

The only other reference I found was in the .ci.yaml itself, which reads:

# The current android emulator config names can be found here:
# https://chromium.googlesource.com/chromium/src.git/+/HEAD/tools/android/avd/proto
# You may use those names for the android_virtual_device version.

... this comment was confusing, because I think the name we're referring to actually lives in the JSON file:

"test_dependencies": [
    {
        "dependency": "android_virtual_device",
        "version": "android_34_google_apis_x64.textpb"
    },
    {
        "dependency": "avd_cipd_version",
        "version": "build_id:8759428741582061553"
    }
]

... leading me to try replacing the "version" key:

-        "version": "android_34_google_apis_x64.textpb"
+        "version": "android_28_google_apis_x86.textpb"

... which appears to be what I need to do, but none of that was covered in the Wiki.

Metadata

Metadata

Assignees

No one assigned

    Labels

    P2Important issues not at the top of the work listteam-infraOwned by Infrastructure teamtriaged-infraTriaged by Infrastructure team

    Type

    No type

    Projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions