Skip to content

Web tests may be too sharded #124682

@zanderso

Description

@zanderso

Here is an example where there is 6.5+ minutes of overhead to run 40s of tests:

https://ci.chromium.org/ui/p/flutter/builders/prod/Linux%20Production%20Engine%20Drone/108269/overview

This may be an artifact of the long source checkout time when there is a cold cache, but even in the case of a warm cache the checkout time appears to be around 30s, so including the other steps, there will still be more overhead than time running tests.

cc @keyonghan @godofredoc @eyebrowsoffire @yjbanov

Metadata

Metadata

Assignees

No one assigned

    Labels

    P2Important issues not at the top of the work listc: contributor-productivityTeam-specific productivity, code health, technical debt.platform-webWeb applications specificallyteam-webOwned by Web platform teamtriaged-webTriaged by Web platform team

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions