Known Issues

DTS202105190IPKB9P1300

Condition: The CTS test suite is used in the CI daily build scenario.

Symptom: Test cases in some modules of the test suite failed to pass corresponding tests in a container. After another container was used, the test cases passed the corresponding tests.

Root cause: In this trouble ticket, the failed test case in 296 CtsUiAutomationTestCases is not a baseline test case but an additional test case. The test case will be further analyzed in the CTS special work.

The failed test case in 26 CtsAssistTestCases is caused by the test case itself, whose Google bug ID is 30859355. This issue may be eligible for an exemption.

Two failed test cases in 69 CtsGraphicsTestCases are related to Vulkan enablement. After the two test cases that do not support the extended properties and image format are masked according to the last CCB decision, this module can pass the test.

From July 2 to September 3, CI CTS daily build was performed for 28 times, among which CtsWidgetTestCases failed for 4 times, CtsJvmtiRunTest993HostTestCases and ctsAtraceHostTestCases each failed once, and CtsAccessibilityTestCases did not fail. The general failure rate is low. Increasing the number of retries can improve the pass rate of the preceding modules.

Impact: The issues in this trouble ticket occurred occasionally. The module with the highest failure rate failed four times in 28 times of CI daily build, and other modules failed once or did not fail. This affected the CTS pass rate in the CI environment.

Minor

Workaround: Increase the number of retries for failed test cases.

Blue zone issue 15

Condition: The video stream cloud phone is used to test Cocos.

Symptom: When playing a game in landscape mode, touch and hold the notification bar and click the home button on the server side. As a result, the notification bar is forcibly pulled out.

Root cause: The blue zone requires that the drop-down notification bar be masked. However, this is not implemented in the complex operation scenario described in the symptom part. As a result, the drop-down notification bar can still be displayed. The masking solution in this scenario is still under discussion and is not modified before this release.

Impact: The trigger conditions are strict. Generally, a user does not press and hold the notification bar with the left hand and press and hold the home button with the right hand at the same time. In addition, this problem occurs only during the switch between landscape and portrait modes. Even if the notification bar is pulled out, the functions are not affected. Therefore, there is almost no impact.

Blue zone

This problem rarely occurs during normal use.

DTS202107210KJTJ7P1400

Condition: Cocos is tested on the video stream cloud phone in the CI daily build scenario.

Symptom: After the Cocos test case is executed during CI video stream daily build, artifacts occur on the home page of the cloud phone on the server.

Root cause: Through CI log analysis, when the Cocos test case is executed, out-of-bounds memory access occurs during function calls in gallium_dri.so of Mesa. As a result, Mesa crashes. The call stack points to the eglSwapBuffersWithDamageKHR interface in the Mesa library, which causes artifacts. It is preliminarily determined that the problem is related to the third-party Mesa driver and needs to be further analyzed.

Impact:

1. There is a low probability that this problem occurs. This problem occurred twice on the video stream daily build server (on July 20 and September 4, with a gap of more than one month). In subsequent 6,000 dedicated tests, this problem did not recur.
2. Only the cloud phone that runs the test case is affected. Other cloud phones started on the server are not affected.

Minor

Restart the cloud phone.

DTS2021090912581

Condition: Upgrade the server firmware (BIOS 177, CPLD 5.14, and iBMC 3.01.12.23).

Symptom: The server (model 5220) uses a new motherboard to upgrade BIOS 177, CPLD 5.14, and iBMC 3.01.12.23, but the upgrade fails, and the server hangs. Currently, no official new versions are available for the new motherboard.

Root cause: Model 5220 has two versions corresponding to the old and new motherboards. The link to the BIOS version matching the old motherboard at the Support website is invalid. In this test, the new motherboard is used. According to the Kunpeng computing hardware developers of the 5220 motherboard, the BIOS version matching the new 5220 motherboard has not been released. If the latest BIOS version on the Support website is used, the upgrade fails. To solve this problem, the BIOS team needs to release the BIOS version matching the new motherboard to the Support website.

Impact: If a customer uses the new motherboard, the customer cannot obtain the matching BIOS version from the Support website.

Minor

None