Skip to content

[windows] add ci tests that run against feature set 10_0 #192899

Closed

Description

@gaaclarke

In #191978 we found that directx feature set 10_0 got broken. We don't have a CI step that makes sure that works. We should add one so that once #191978 is fixed we can continue to make sure it works.

Activity

  1. added
    c: new featureNothing broken; request for a new capability
    P2Important issues not at the top of the work list
    on Sep 16, 2026
  2. gaaclarke commented on Sep 23, 2026

    @gaaclarke
    MemberAuthor

    Some ideas are:

    1. Set up ANGLE with flags that limit it's capabilites to match feature set 10_0
    2. Come with some sort of way to set up machine to switch directx 9 capabilities

    I think we just need a smoke test for now to make sure we haven't completely busted rendering, like what has happened previously.

  3. self-assigned this
    on Oct 9, 2026
  4. b-luk commented on Oct 19, 2026

    @b-luk
    Contributor

    Added a compositor test for feature level 10_0 in #194114, and added a renderer golden test in #194321. Marking as completed.

  5. github-actions commented on Nov 2, 2026

    @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.

  6. locked as resolved and limited conversation to collaborators on Nov 2, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

P2Important issues not at the top of the work listc: new featureNothing broken; request for a new capabilityteam-engineOwned by Engine teamtriaged-engineTriaged by Engine team

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions