Skip to content

Cherry picks to the engine require formatting #149319

@reidbaker

Description

@reidbaker

In 2 instances in the past month cherry picks required formatting to pass engine pr process.

Figure out why formatting is not being required in the engine on java code or what causes the difference between cherry picks and regular merges.

CP that needed formatting
flutter/engine#52982
Failing test https://ci.chromium.org/ui/p/flutter/builders/try/Linux%20Engine%20Drone/2350870/overview
Original PR
flutter/engine#52980
Passing Test
https://logs.chromium.org/logs/flutter/buildbucket/cr-buildbucket/8747221866092111153/+/u/test:_test:_Check_formatting/stdout

Second example
flutter/engine#52987

Metadata

Metadata

Assignees

Labels

P1High-priority issues at the top of the work listplatform-androidAndroid applications specificallyteam-androidOwned by Android platform team

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions