Skip to content

Clang tidy output in the engine has regressed, making debugging difficult #145926

@matanlurey

Description

@matanlurey

From @dkwingsmt on an internal chat:

For some reason our engine CI no longer prints the actual error of the clang tidy check, but a bunch of useless logs, such as in
https://logs.chromium.org/logs/flutter/buildbucket/cr-buildbucket/8752198650857229249/+/u/test:_test:_lint_host_debug/stdout?format=raw
Is it a known issue?

It is now! Definitely a regression, we need to fix this.

Metadata

Metadata

Assignees

Labels

P1High-priority issues at the top of the work listc: tech-debtTechnical debt, code quality, testing, etc.engineflutter/engine related. See also e: labels.

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions