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
cull_opacity_perf__timeline_summary is failing #51148
Devicelab cull_opacity_perf__timeline_summary test failing with 30 second timeout exception.
2020-02-20T14:46:42.632566: stdout: [+29502 ms] 00:30 �[32m+0�[0m�[31m -1�[0m: cull_opacity_perf �[1m�[31m[E]�[0m�[0m
2020-02-20T14:46:42.634427: stdout: [ +2 ms] TimeoutException after 0:00:30.000000: Test timed out after 30 seconds. See https://pub.dev/packages/test#timeouts
This seems like it's different from the last time this benchmark was timing out, but its' a similar issue - the timeline JSON has grown significantly, the test is timing out, and it's gotten slower. I'm reverting the engine change until we figure ithis out.
Apparently this is a duplicate of the original cause in #50997 - the same problem managed to roll in again. @jason-simmons is working on a roll that gets us past it.
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
dnfield commentedon Feb 21, 2020
This seems like it's different from the last time this benchmark was timing out, but its' a similar issue - the timeline JSON has grown significantly, the test is timing out, and it's gotten slower. I'm reverting the engine change until we figure ithis out.
dnfield commentedon Feb 21, 2020
Apparently this is a duplicate of the original cause in #50997 - the same problem managed to roll in again. @jason-simmons is working on a roll that gets us past it.
dnfield commentedon Feb 22, 2020
Going to close this - the offending commit got reverted, and the next roll should roll past it.
github-actions commentedon Aug 22, 2021
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.