939750 - test_ftu_skip_tour freezes when trying to save the email address

Status: RESOLVED FIXED

(Firefox OS Graveyard :: General, defect)

Description

[Viorela Ioia [:viorela]]

Attachment: screenshot.png

Comment 1

[Viorela Ioia [:viorela]]

Device: Inari
Gecko  http://hg.mozilla.org/mozilla-central/rev/a475f94bb1b1
Gaia  9e3012065962019fa86448daa83b60a9072e9093
BuildID 20131116040201
Version 28.0a1

Prerequisities:
Wifi is enabled

Steps to reproduce:
Launch FTU app
Follow steps till you get to About Firefox OS page
Insert an email address
Tap next

Expected results:
Next page is displayed

Actual results:
The tests freezes when saving email

Comment 2

[Jason Smith [:jsmith]]

Can this be manually reproduced outside of automation?

Comment 3

[Viorela Ioia [:viorela]]

Yes, I also tested manually before adding the bug.

Comment 4

[Jason Smith [:jsmith]]

(In reply to Viorela Ioia [:viorela] from comment #3)
> Yes, I also tested manually before adding the bug.

Okay. Second question I have is:

Do you know when the test last passed when it first failed?

Specifically, I'm looking to know the gaia/gecko changesets & build date of the build that had the test last pass & when it first failed.

Comment 5

[Viorela Ioia [:viorela]]

I don't know. I just ran the test today and it failed. I don't know when was the last time it worked.

Comment 6

[Viorela Ioia [:viorela]]

Last passing build:
Gaia:     ac42cb33f21b3f13595432c965f44615daae2225
Gecko:    http://hg.mozilla.org/mozilla-central/rev/b2fab608772f
BuildID   20131115040200
Version   28.0a1

First failing build:
Gaia:     9e3012065962019fa86448daa83b60a9072e9093
Gecko:    http://hg.mozilla.org/mozilla-central/rev/a475f94bb1b1
BuildID   20131116040201
Version   28.0a1

Comment 7

[Jason Smith [:jsmith]]

Can someone get a logcat when reproducing this bug?

Comment 8

[Sarah Parsons]

Attachment: FTU_Email_Logcat

Comment 9

[Sarah Parsons]

Logcat is now attached.

Comment 10

[Jason Smith [:jsmith]]

(In reply to Sarah Parsons from comment #9)
> Logcat is now attached.

Can you double check the regression range as well manually?

Comment 11

[Sarah Parsons]

The regression range in comment 6 is correct. 

This issue starts to occur on the Buri 1.3 Build ID: 20131116040201

Gaia   9e3012065962019fa86448daa83b60a9072e9093
SourceStamp a475f94bb1b1
BuildID 20131116040201
Version 28.0a1

Last Working Buri 1.3 Build ID: 20131115040200

Gaia   ac42cb33f21b3f13595432c965f44615daae2225
SourceStamp b2fab608772f
BuildID 20131115040200
Version 28.0a1

Comment 12

[Jason Smith [:jsmith]]

http://hg.mozilla.org/mozilla-central/pushloghtml?fromchange=b2fab608772f&tochange=a475f94bb1b1

Comment 13

[Benoit Jacob [:bjacob] (mostly away)]

As I said on bug 939769 comment 11:

It's not impossible that this would be caused by the surface renewal stuff that I landed in that regression range, bug 925608, but it's not certain. The best thing to do here is to bisect this down to 1 changeset. If the culprit is among my patches, the good news is that they're split into a sequence of small patches that should each run correctly, so bisection down to 1 cset will probably pinpoint a very specific issue.

Comment 14

[Jason Smith [:jsmith]]

(In reply to Benoit Jacob [:bjacob] from comment #13)
> As I said on bug 939769 comment 11:
> 
> It's not impossible that this would be caused by the surface renewal stuff
> that I landed in that regression range, bug 925608, but it's not certain.
> The best thing to do here is to bisect this down to 1 changeset. If the
> culprit is among my patches, the good news is that they're split into a
> sequence of small patches that should each run correctly, so bisection down
> to 1 cset will probably pinpoint a very specific issue.

After talking with some folks in IRC, I think this was caused by bug 927196.

Comment 15

[Jason Smith [:jsmith]]

See https://bugzilla.mozilla.org/show_bug.cgi?id=939769#c15.