Skip to content

Add a test after every shard to make sure we're not leaving the git workspace in a modified state after running tests #78265

@Hixie

Description

@Hixie

We should do this on LUCI.

This https://github.com/flutter/flutter/pull/77100/files shows what it would look like for Cirrus (where we could do it as well, if we do it on LUCI, but we shouldn't only do it on Cirrus).

Metadata

Metadata

Assignees

No one assigned

    Labels

    P3Issues that are less important to the Flutter projecta: tests"flutter test", flutter_test, or one of our testsc: contributor-productivityTeam-specific productivity, code health, technical debt.c: tech-debtTechnical debt, code quality, testing, etc.team-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