[CP-stable]In flutter_test_performance, consider the blank line at the start of "flutter test" output to be optional.#182335
Merged
Conversation
…"flutter test" output to be optional. (flutter#180911) flutter_test_performance runs a "flutter test" command and parses its output. The parser expects the output to begin with a blank line. That line is no longer present after the roll to version 1.29 of the Dart test package (see flutter#180886) Fixes flutter#180903
Contributor
Author
|
@camsim99 please fill out the PR description above, afterwards the release team will review this request. |
|
This pull request was opened from and to a release candidate branch. This should only be done as part of the official Flutter release process. If you are attempting to make a regular contribution to the Flutter project, please close this PR and follow the instructions at Tree Hygiene for detailed instructions on contributing to Flutter. Reviewers: Use caution before merging pull requests to release branches. Ensure the proper procedure has been followed. |
Contributor
There was a problem hiding this comment.
Code Review
This pull request updates the flutter_test_performance devicelab test to handle variations in flutter test output. The change makes an initial blank line in the output optional by adjusting the state machine that parses the test output. This ensures the test works correctly with different versions of the Dart test package, some of which no longer produce this blank line. The corresponding code comment has also been updated for clarity. The change is correct and improves the test's robustness.
582a0e7
into
flutter:flutter-3.41-candidate.0
141 checks passed
engine-flutter-autoroll
added a commit
to engine-flutter-autoroll/packages
that referenced
this pull request
Feb 13, 2026
…line at the start of "flutter test" output to be optional. (flutter/flutter#182335)
engine-flutter-autoroll
added a commit
to engine-flutter-autoroll/packages
that referenced
this pull request
Feb 13, 2026
…line at the start of "flutter test" output to be optional. (flutter/flutter#182335)
engine-flutter-autoroll
added a commit
to engine-flutter-autoroll/packages
that referenced
this pull request
Feb 14, 2026
…line at the start of "flutter test" output to be optional. (flutter/flutter#182335)
engine-flutter-autoroll
added a commit
to engine-flutter-autoroll/packages
that referenced
this pull request
Feb 20, 2026
…line at the start of "flutter test" output to be optional. (flutter/flutter#182335)
engine-flutter-autoroll
added a commit
to engine-flutter-autoroll/packages
that referenced
this pull request
Feb 20, 2026
…line at the start of "flutter test" output to be optional. (flutter/flutter#182335)
engine-flutter-autoroll
added a commit
to engine-flutter-autoroll/packages
that referenced
this pull request
Feb 21, 2026
…line at the start of "flutter test" output to be optional. (flutter/flutter#182335)
Xbectordash
pushed a commit
to Xbectordash/abhi_flutter_fork
that referenced
this pull request
May 13, 2026
…e start of "flutter test" output to be optional. (flutter#182335) This pull request is created by [automatic cherry pick workflow](https://github.com/flutter/flutter/blob/main/docs/releases/Flutter-Cherrypick-Process.md#automatically-creates-a-cherry-pick-request) Please fill in the form below, and a flutter domain expert will evaluate this cherry pick request. ### Issue Link: What is the link to the issue this cherry-pick is addressing? flutter#180903. This is blocking a stable hotfix right now. See https://ci.chromium.org/ui/p/flutter/builders/prod/Linux_mokey%20flutter_test_performance/8971/overview. ### Impact Description: Maybe impacts some people parsing test output besides us. ### Changelog Description: Version 1.29 of the Dart test package adds a blank line to test output causing unexpected test failures. ### Workaround: No need for a workaround/ ### Risk: What is the risk level of this cherry-pick? ### Test Coverage: Are you confident that your fix is well-tested by automated tests? ### Validation Steps: What are the steps to validate that this fix works? < Replace with validation steps here >
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
5 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This pull request is created by automatic cherry pick workflow
Please fill in the form below, and a flutter domain expert will evaluate this cherry pick request.
Issue Link:
What is the link to the issue this cherry-pick is addressing?
#180903. This is blocking a stable hotfix right now. See https://ci.chromium.org/ui/p/flutter/builders/prod/Linux_mokey%20flutter_test_performance/8971/overview.
Impact Description:
Maybe impacts some people parsing test output besides us.
Changelog Description:
Version 1.29 of the Dart test package adds a blank line to test output causing unexpected test failures.
Workaround:
No need for a workaround/
Risk:
What is the risk level of this cherry-pick?
Test Coverage:
Are you confident that your fix is well-tested by automated tests?
Validation Steps:
What are the steps to validate that this fix works?
< Replace with validation steps here >