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
Create utility function to pass ProcessResult along with anticipated exit code + implement within flakes #127135
This utility function will be used in integration tests to check the result of a process to ensure the exit code expected is returned, if the exit code returned is not what was expected, the function will print out the stdout, stderr, and exit_code
changed the title [-]Create utility function to pass `ProcessResult` along with anticipated exit code[/-][+]Create utility function to pass `ProcessResult` along with anticipated exit code + implement within flakes[/+]on May 30, 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
eliasyishak commentedon May 18, 2023
fyi @christopherfujino
christopherfujino commentedon May 19, 2023
Ooh, if you want to be fancy this can be a matcher. Here's some prior art: https://github.com/flutter/flutter/blob/master/packages/flutter_tools/test/src/common.dart#LL91C62-L91C62
`ProcessResultMatcher` created and used in test (#127414)
[-]Create utility function to pass `ProcessResult` along with anticipated exit code[/-][+]Create utility function to pass `ProcessResult` along with anticipated exit code + implement within flakes[/+]eliasyishak commentedon May 30, 2023
After #127414 landed, implementing in flakes identified below
[flutter_tools] Use process matcher for multidex test (#127996)
[flutter_tools] Migrate more integration tests to process result matc…
github-actions commentedon Jun 16, 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 -vand a minimal reproduction of the issue.