Skip to content

Add more detailed logging to clang-tidy CI step #131689

@eyebrowsoffire

Description

@eyebrowsoffire

The flutter engine's clang-tidy step has been timing out fairly consistently. Unfortunately, the log doesn't give us enough information to know which task is stalled. We probably need to add some more info to the logs to better understand this issue, including:

  • Timestamps on each log statement to understand timing better
  • Log statements about when a job starts or stops

Metadata

Metadata

Assignees

No one assigned

    Labels

    c: contributor-productivityTeam-specific productivity, code health, technical debt.c: flakeTests that sometimes, but not always, incorrectly passteam-engineOwned by Engine team

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions