Skip to content

Add a --dry-run to test.dart to observe what shards run what tests #158884

@matanlurey

Description

@matanlurey

@matanlurey:

Is there a deterministic (by humans) way of mapping a package/foo/test/foo_test.dart to the task and shard it is executing on? I'd settle for "I know the task, tell me the shard" if that is all we have.

For example, imagine the query:
"I am a test owner of package/foo/test, and I want to see if foo_test.dart is running slowly"

@christopherfujino:

There is a deterministic way, but it's not easy. We could add a special flag to test.dart though, that doesn't actually run any tests but prints out what tests would have run on which shard. this seems useful

Metadata

Metadata

Assignees

Labels

P2Important issues not at the top of the work lista: tests"flutter test", flutter_test, or one of our teststeam-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