Skip to content

engine: misleading exception message in font_subset test script #145412

@selfisekai

Description

@selfisekai

flutter/engine#51492

font_subset tests previously were hardcoded to look for the binary in specific build variants, and got later changed (in flutter/engine#50327) to require an explicit variant as an argument

little nitpick: the exception message still hardcodes variants instead of naming the one being actually checked

Metadata

Metadata

Assignees

No one assigned

    Labels

    P2Important issues not at the top of the work listengineflutter/engine related. See also e: labels.r: fixedIssue is closed as already fixed in a newer versionteam-engineOwned by Engine team

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions