923033 - Investigate why test_dialer.py fails only in automation

Status: RESOLVED WONTFIX

(Firefox OS Graveyard :: Gaia::UI Tests, defect)

Description

[Zac C (:zac)]

test_dialer.py fails during automation causing a crash but it does not fail when the test case is performed manually.

In the past this has pointed towards a marionette issue where it switches frames too quickly or slowly or somesuch.

Can someone debug this test a bit? for example add in some sleeps or debug points to slow the test down and see if we can either make the test work and possibly identify what is causing it to fail only in automation.

Comment 1

[Florin Strugariu [:Bebe]]

The test is failing because of the locator:
https://github.com/mozilla-b2g/gaia/blob/master/tests/python/gaia-ui-tests/gaiatest/apps/phone/regions/call_screen.py#L16

But with that fixed the phone will crash after a few min.

The crashing bug:
Bug 914823 - crash in mozilla::gl::SharedSurface_Gralloc::~SharedSurface_Gralloc

This is crashing because of tearDown()
https://github.com/mozilla-b2g/gaia/blob/master/tests/python/gaia-ui-tests/gaiatest/tests/functional/dialer/test_dialer.py#L40


What I think is going on there:

Call screen has some hooks in the Active call API. 

After we run the test (Make a call and do our asserts);
In the test tearDown  we kill all active calls. With that Outgoing call screen is also closed.

Something remains "connected" between "active call API" and "Dialer app" and throws a error 
E/GeckoConsole( 2692): [JavaScript Warning: "Error in parsing value for 'font-size'.  Declaration dropped." {file: "app://communications.gaiamobile.org/dialer/index.html#keyboard-view" line: 0 column: 0 source: "40"}]

After a while we see in the logcat:
I/Gecko   ( 2692): [SharedSurface_Gralloc 0x43da9740] destroyed
I/Gecko   ( 2573):
I/Gecko   ( 2573): ###!!! [Parent][MessageChannel] Error: Channel error: cannot send/recv

And off course:
I/GeckoDump( 2573): Crash reporter : Can't fetch app.reportCrashes. Exception: [Exception... "Component returned failure code: 0x8000ffff (NS_ERROR_UNEXPECTED) [nsIPrefBranch.getBoolPref]"  nsresult: "0x8000ffff (NS_ERROR_UNEXPECTED)"  location: "JS frame :: chrome://browser/content/shell.js :: shell_reportCrash :: line 120"

Comment 2

[Florin Strugariu [:Bebe]]

Attachment: logcat of the crash after the test passes

Comment 3

[Zac C (:zac)]

Interesting info thanks Bebe. I am seeing similar behaviour.

What is your recommendation -  do you think we can remove the tearDown and re-enable the test?

Comment 4

[Florin Strugariu [:Bebe]]

Attachment: Pointer to Github pull request: https://github.com/mozilla-b2g/gaia/pull/12615

Pointer to Github pull-request

Comment 5

[Florin Strugariu [:Bebe]]

Comment on attachment 813096 [details]
Pointer to Github pull request: https://github.com/mozilla-b2g/gaia/pull/12615

This will fix the test 
But the crash will still affect us after the test passes

Comment 6

[Florin Strugariu [:Bebe]]

I also added a workaround for the crash

Comment 7

[Zac C (:zac)]

Comment on attachment 813096 [details]
Pointer to Github pull request: https://github.com/mozilla-b2g/gaia/pull/12615

2 comments in the PR

Comment 8

[[:AndreiH]]

My comments are in the pull request

Comment 9

[Bob Silverberg [:bsilverberg]]

From the pull request:

Zac: This test passes fine on the Hamachi device without this tweak so I'm going to close this pull request and unxfail it elsewhere.

Comment 10

[Zac C (:zac)]

Thanks Bob I'm a bit behind on this pull/bug link up :)