Skip to content

Print the backtrace explicitly when assertions are tripped in all unit-test harnesses. #50244

@chinmaygarde

Description

@chinmaygarde

The process dying without a backtrace makes fixing issues like this hard to diagnose. A previous attempt of this endeavor was abandoned and must be revived and carried to completion.

Metadata

Metadata

Assignees

Labels

c: flakeTests that sometimes, but not always, incorrectly passengineflutter/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