1119504 - [raptor] Launch_test sometimes hangs after app close (when running on b2g-emulator)

Status: RESOLVED WONTFIX

(Firefox OS Graveyard :: Gaia::PerformanceTest, defect)

Description

[Robert Wood [:rwood]]

Attachment: logcat.txt

The raptor launch_test sometimes hangs after killing the app. Stdout:

rwood@ubuntu:~/gaia$ DEBUG=* RUNS=1 RAPTOR_EMULATOR=1 APPS="communications/dialer" RAPTOR_DATA_GAIA_REV=$(git rev-parse HEAD) node tests/raptor/launch_test.js 
  raptor:device [Logging] Clearing Log +0ms
  raptor:command [Executing Command] adb logcat -c +2ms
  raptor:device [Restarting B2G] +3ms
  raptor:command [Executing Command] adb shell stop b2g && adb shell start b2g +0ms
  adb:command Send '000Chost:devices' +0ms
  adb:command Send '001Chost:transport:emulator-5554' +5ms
  adb:command Send '000Dshell:getprop' +2ms
  adb:command Send '001Chost:transport:emulator-5554' +121ms
  adb:command Send '0005sync:' +0ms
  adb:sync SEND /data/local/orng,33188 +0ms
  adb:command Send '001Chost:transport:emulator-5554' +6ms
  adb:command Send '0020shell:chmod 777 /data/local/orng' +0ms
  adb:sync DONE +5ms
  raptor:device [Logging] Clearing Log +408ms
  raptor:command [Executing Command] adb logcat -c +0ms
  raptor:coldlaunch Waiting for homescreen +102ms
  adb:command Send '001Chost:transport:emulator-5554' +1.4m
  adb:command Send '0043shell:echo "drag 250 250 250 350 10 150" > /data/local/tmp/orng-cmd' +0ms
  adb:command Send '001Chost:transport:emulator-5554' +7ms
  adb:command Send '0041shell:/data/local/orng /dev/input/event0 /data/local/tmp/orng-cmd' +1ms
[Test] Starting run 1
  raptor:coldlaunch [Launching] communications/dialer application +2m
  raptor:coldlaunch [Launching] Translate to device pixels (X: 120 => 120, Y: 233 => 233) +0ms
  raptor:coldlaunch [Launching] Triggering device tap on application icon +0ms
  adb:command Send '001Chost:transport:emulator-5554' +6s
  adb:command Send '0037shell:echo "tap 120 233 1 1" > /data/local/tmp/orng-cmd' +1ms
  adb:command Send '001Chost:transport:emulator-5554' +5ms
  adb:command Send '0041shell:/data/local/orng /dev/input/event0 /data/local/tmp/orng-cmd' +0ms
  raptor:coldlaunch Received performance entry `navigationLoaded` +3s
  raptor:coldlaunch Received performance entry `visuallyLoaded` +6ms
  raptor:coldlaunch Received performance entry `contentInteractive` +9ms
  raptor:coldlaunch Received performance entry `navigationInteractive` +33ms
  raptor:coldlaunch Received performance entry `fullyLoaded` +2s
  raptor:device [Logging] +1ms Memory Entry: Communications|$(b2g-info | grep "Communications")
  raptor:command [Executing Command] adb shell 'log -p i -t GeckoConsole "Memory Entry: Communications|$(b2g-info | grep "Communications")"' +0ms
[Test] Run 1 complete
  raptor:device [Closing App] PID 8976 +1s
  raptor:command [Executing Command] adb shell kill 8976 +0ms

Raptor hangs at that point. Notice above that the 'appLaunch' performance entry was not received. That is the case everytime this happens. In attached logcat, the 'launchApp' event was received AFTER the app was killed and the homescreen was loaded again.

Comment 1

[Robert Wood [:rwood]]

These seems to have been fixed somehow by other changes.