Fixed
Status Update
Comments
me...@oppo.corp-partner.google.com <me...@oppo.corp-partner.google.com> #2
build id:OPPO/PKH110/OP5DC1L1:15/AP3A.240617.008/V.1b4bd52_11_1:user/release-keys
vi...@google.com <vi...@google.com> #3
We have shared this with our product and engineering team and will update this issue with more information as it becomes available.
me...@oppo.corp-partner.google.com <me...@oppo.corp-partner.google.com> #4
Thank you very much. I hope to get a quick response. Is it a omission skip cts test cases for foldable screen? Can we apply for an exemption?
vi...@google.com <vi...@google.com> #5
The issue has been fixed and watch out for future releases, Thanks.
Description
ANDROID OS VERSION:35
STEPS TO REPRODUCE: (please be specific)
1. Using Google's latest CTS suite:15_r2
2.run cts -m CtsGameFrameRateTestCases[foldable:99:ALL]
[Please include a screenshot or video showing the issue]
REPRODUCE RATE:
10 times out of 10 tries
OBSERVED RESULTS:
There was 1 failure:
1) testGameModeBackpressure(android.gameframerate.cts.GameFrameRateTest)
java.lang.AssertionError: Game Mode Override(30), expectedFrameRate(30.00 30.00): choreographer observed refresh rate doesn't match the current refresh rate. expected: (30.00, 30.00) observed: 85.09
EXPECTED RESULTS:
pass
REPRODUCIBLE on Pixel/SoC Reference Device (required): Yes
Dear GOOGLE:
Currently, this test item can only be tested on foldable screens or tablets. It cannot be tested on straight triggers due to skip.
We analyzed and found that the test item of this module has been removed in the new tool.
However, there is a foldable module with foldable attribute, which is not matched and removed, and there will be a problem that the foldable screen fails to run CtsGameFrameRateTestCases.
Please ask whether these test item needs to be removed in the foldable screen scene