Fix ACTS failures on qemuarm

marked this issue as related to #18 (closed)

changed milestone to %goofy beta

changed the description

changed iteration to *iteration:14

set weight to 10

marked this issue as related to #52 (closed)

According to a replay from jiyong@huawei.com on 06-Aug-22 10:13 to our email regarding Public base library (some tests are present in the //test/xts/acts/compileruntime:compileruntime but are not being built) and Distributed task scheduling (no tests whatsoever are present in the /test/xts/acts directory):

OpenHarmony 3.0.1-LTS version, a test suite with two components missing from the minimal test set introspection table:

Public base library

Distributed task scheduling

Please approve Oniro Compatibility Test without building and testing both components.

---This part does not need to be tested

@mrybczyn @esben FYI

changed the description

It turned out that haps generated in meta-openharmony are broken. Until that is sorted out for debugging / testing using ACTS haps built in vanilla OpenHarmony-LTS-3.0.1 build.

closed

reopened

assigned to @robertd

Comparing qemu and HiTaurus board logs from running ActsStartupJSApiTest.json following failure happens on qemu:

08-12 10:17:54.427   465   473 I 03b00/JSApp: app Log: start################################start
08-12 10:17:54.445   465   475 E 03900/Ace: [card_transition_controller.cpp(operator())] handle event: 3 failed. unknown event.
08-12 10:17:54.508   255   255 W 01510/IPCObjectProxy: SendObituary: handle = 16 call OnRemoteDied
08-12 10:17:54.509   255   255 I 01510/IPCWorkThreadPool: 60: SpawnThread Name= 4IPC
08-12 10:17:54.509   255   255 I 01510/IPCWorkThreadPool: 67: SpawnThread, now idleThreadNum_ =11
08-12 10:17:54.509   255   255 I 01510/IPCWorkThread: void OHOS::IPCWorkThread::Start(int, int, std::string) 87: create thread = 4IPC255_255, policy=0, proto=0
08-12 10:17:54.509   255   255 W 01510/IPCObjectProxy: SendObituary: handle = 17 call OnRemoteDied
08-12 10:17:54.510   255   255 E 01000/AbilityManagerService: [ability_scheduler_stub.cpp(OnRemoteDied:565)]recv AbilitySchedulerRecipient death notice
08-12 10:17:54.510   255   255 D 01000/AbilityManagerService: [ability_record.cpp(OnSchedulerDied:851)]On scheduler died.
08-12 10:17:54.510   255   255 I 01000/AbilityManagerService: [ability_record.cpp(OnSchedulerDied:880)]Ability on scheduler died: 'ohos.acts.startup.js.function.MainAbility'
08-12 10:17:54.511   218   372 W 01510/IPCObjectProxy: SendObituary: handle = 3 call OnRemoteDied
08-12 10:17:54.518   255   330 E 01110/AppMgrService: [app_mgr_service_inner.cpp(OptimizerAbilityStateChanged):989] process optimizer is not init
08-12 10:17:54.518   255   330 E 01110/AppMgrService: [app_mgr_service_inner.cpp(OptimizerAppStateChanged):1039] process optimizer is not init
08-12 10:17:54.519   255   330 W 01510/IPCObjectProxy: not databus dbinder, need do nothing
08-12 10:17:54.519   255   330 W 01510/IPCObjectProxy: handle = 16 destroyed
08-12 10:17:54.529   218   372 W 01510/IPCObjectProxy: not databus dbinder, need do nothing
08-12 10:17:54.530   218   372 W 01510/IPCObjectProxy: handle = 3 destroyed
08-12 10:17:54.541   255   285 I 01000/AbilityManagerService: [ability_stack_manager.cpp(OnAbilityDied:2059)]On ability died.

Reason of this failure is not yet known.

As it turned out, tests are not being executed when they are started from onShow() method in HAP index.js. With following patch in //test/xts/acts:

diff --git a/startup/startup_standard/src/main/js/default/pages/index/index.js b/startup/startup_standard/src/main/js/default/pages/index/index.js
index 173f299a..0466f9fc 100644
--- a/startup/startup_standard/src/main/js/default/pages/index/index.js
+++ b/startup/startup_standard/src/main/js/default/pages/index/index.js
@@ -24,8 +24,7 @@ export default {
     },
     onInit() {
         this.title = this.$t('strings.world');
-    },
-    onShow() {
+
         console.info('onShow finish')
         const core = Core.getInstance()
         const expectExtend = new ExpectExtend({
@@ -41,6 +40,8 @@ export default {
         require('../../test/List.test')
         core.execute()
     },
+    onShow() {
+    },
     onReady() {
     },
 }

ActsStartupJSApiTest.json test suite has a pass ratio of 63/92 (it may be higher as the test suite exits on first failure).

I expect similar patch will enable executing rest of the ACTS hap tests.

Vanilla OpenHarmony-3.0.1 acts test suite acts-suites.tgz

You have listed ActsWifiJSApiTest.json. Does this belong to our list of mandatory tests when we don't have wifi support?

It was marked as mandatory. We'll need to discus it.

changed iteration to *iteration:15

Tests that pass with test code executed from onInit instead of onShow:

Testcase ActsOsAccountJSApiTest.json: PASS
total cases:7;failure 0,error 0,pass 7; consuming 4.35S

Testcase ActsAmsDataUriUtilsTest.json: PASS
total cases:20;failure 0,error 0,pass 20; consuming 10.34S

marked the checklist item ActsOsAccountJSApiTest.json - HAP doesn't produce result - timeout or test failure as completed

marked the checklist item //test/xts/acts/account:account as completed

marked the checklist item ActsAmsDataUriUtilsTest.json - HAP doesn't produce result - timeout or test failure as completed

changed the description

marked the checklist item ActsStartupJSApiTest.json - 63/92 as completed

marked the checklist item ActsPowerMgrBatteryTest.json - 24/35 as completed

marked the checklist item //test/xts/acts/startup:startup as completed

marked the checklist item //test/xts/acts/powermgr:powermgr as completed

changed the description

marked the checklist item //test/xts/acts/distributeddatamgr:distributeddatamgr as completed

changed the description

Fix ACTS failures on qemuarm

Child items 0

Activity

Fix ACTS failures on qemuarm

Relates to

Activity