Skip to content

Revert "Shader warm up (#27660)" #28376

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Merged
liyuqian merged 1 commit into from
Feb 23, 2019
Merged

Revert "Shader warm up (#27660)" #28376

liyuqian merged 1 commit into from
Feb 23, 2019

Conversation

@liyuqian
Copy link
Contributor

@liyuqian liyuqian commented Feb 23, 2019

This reverts commit a44f174.

Reason: start_up tests become flaky.

See #28374

TBR: xster

@liyuqian
Revert "Shader warm up (flutter#27660)"
3c8cb21 
This reverts commit a44f174.

Reason: start_up tests become flaky.

See flutter#28374

TBR: xster
@liyuqian liyuqian requested a review from xster February 23, 2019 01:32
@liyuqian liyuqian merged commit adc8e15 into flutter:master Feb 23, 2019
@zoechi zoechi added engine flutter/engine related. See also e: labels. c: performance Relates to speed or footprint issues (see "perf:" labels) c: contributor-productivity Team-specific productivity, code health, technical debt. team: flakes and removed engine flutter/engine related. See also e: labels. c: performance Relates to speed or footprint issues (see "perf:" labels) labels Feb 25, 2019
@miguelcmedeiros miguelcmedeiros mentioned this pull request Feb 25, 2019
Closed
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Aug 7, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Reviewers

@xster xster Awaiting requested review from xster

Assignees

No one assigned

Labels

c: contributor-productivity Team-specific productivity, code health, technical debt.

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

3 participants

@liyuqian @zoechi @googlebot