Skip to content
This repository was archived by the owner on Feb 25, 2025. It is now read-only.

Conversation

@GaryQian
Copy link
Contributor

Reverts #9260

Although the exact cause has not been identified, it is most likely the regressions we have been seeing in various benchmarks originates in this change.

Since this seems to not want to repro locally, I propose we temporarily roll this back and see if it fixes it. There are only 3 commits in flutter/flutter@6d0e618 and this seems, out of 3 unlikely commits, to be the most likely one mostly because the other two commits are very small and mostly trivial.

Copy link
Contributor

@tvolkert tvolkert left a comment

Choose a reason for hiding this comment

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

LGTM

@jason-simmons
Copy link
Member

Do we have any way to experiment with different engine and framework builds in the device lab?

So far we haven't been able to reproduce the benchmark regressions in other environments. I'd be curious to try doing another run of the benchmarks in the lab with flutter/flutter@e59d9a8 versus flutter/flutter@6d0e618 to confirm that the variation in benchmark results is consistently tied to the engine roll.

@GaryQian
Copy link
Contributor Author

Prefer fix forward instead.

@GaryQian GaryQian closed this Jun 13, 2019
@dnfield dnfield deleted the revert-9260-elf_library_flag branch June 27, 2019 22:26
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants