You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Enable regular validation for leaks in Flutter Framework. #138741
This PR adds flag to turn leak tracking on/off for flutter tests: #138653
Leak tracking is off by default till prove of its stability.
To prove leak tracker stability we need a signal about leak related failures on master. Ideally, after each PR. If it not possible, just regular execution of flutter tests with flag enabled.
This would be command to run in flutter/packages/flutter:
flutter test --dart-define=flutter_test_config.leak_tracking=true
Ideally I would like to see output of three types:
(green) Tests passed
(red) Tests failed and there is text Which: contains leaks: in stdout
(yellow) Test failed without text Which: contains leaks: in stdout
For example, it can be just email with color in the subject, like:
leak_traker report after merge of PR 123: green
I am open for any trade offs and adjustments, to make it compliant with prior art add to make it easier to configure..
changed the title [-]Enable regular validation for reaks in Flutter Framework.[/-][+]Enable regular validation for leaks in Flutter Framework.[/+]on Nov 21, 2023
This thread has been automatically locked since there has not been any recent activity after it was closed. If you are still experiencing a similar issue, please open a new bug, including the output of flutter doctor -v and a minimal reproduction of the issue.
Activity
polina-c commentedon Nov 20, 2023
@godofredoc , created this issue as we discussed
[-]Enable regular validation for reaks in Flutter Framework.[/-][+]Enable regular validation for leaks in Flutter Framework.[/+]polina-c commentedon Dec 20, 2023
Closing in favor of #140414
github-actions commentedon Jan 4, 2024
This thread has been automatically locked since there has not been any recent activity after it was closed. If you are still experiencing a similar issue, please open a new bug, including the output of
flutter doctor -vand a minimal reproduction of the issue.