Skip to content

Detect benchmarks as tests in engine repo#1392

Merged
fluttergithubbot merged 2 commits intoflutter:mainfrom
dnfield:master
Oct 13, 2021
Merged

Detect benchmarks as tests in engine repo#1392
fluttergithubbot merged 2 commits intoflutter:mainfrom
dnfield:master

Conversation

@dnfield
Copy link
Contributor

@dnfield dnfield commented Oct 13, 2021

Engine uses things like shell_benchmarks.cc for benchmark related tests.

@xster fyi

Another attempt here, this time starting witht he right base.

Copy link
Contributor

@keyonghan keyonghan left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM with tests passing.

@dnfield
Copy link
Contributor Author

dnfield commented Oct 13, 2021

Whups - fixed the regex. It needed to be (tests?|benchmarks?), not (tests|benchmarks)?

@dnfield dnfield added the waiting for tree to go green Merge PR when tree becomes green via fluttergithubbot label Oct 13, 2021
@fluttergithubbot fluttergithubbot merged commit 38ac56b into flutter:main Oct 13, 2021
@chinmaygarde
Copy link

chinmaygarde commented Oct 13, 2021

I think we should revert this because... a benchmark is not a test. While the benchmark may exercise code newly added or modified along the way. How fast something is orthogonal to its correctness.

@dnfield
Copy link
Contributor Author

dnfield commented Oct 13, 2021

But some changes are only covered by benchmarks right?

@dnfield
Copy link
Contributor Author

dnfield commented Oct 13, 2021

My particular change may need a different test, but it seems fair to leave it to reviewers rather than the bot whether a particular change needs a benchmark or unit test

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

waiting for tree to go green Merge PR when tree becomes green via fluttergithubbot

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants