1194425 - test_sms_notification.py: "IndexError: list index out of range."

Status: RESOLVED FIXED

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

Description

[Nicholas Nelson [:NicholasN]]

Description:

Several tests relating to communications (sms, mms, calls) are failing. Based on the screenshots in the HTML reports, it appears that the devices running the automated tests do not have a data connection. These test are passing when local devices are used.

http://jenkins1.qa.scl3.mozilla.com/job/flame-kk-319.mozilla-central.nightly.ui.functional.non-smoke.unstable/16/HTML_Report/

http://jenkins1.qa.scl3.mozilla.com/view/UI/job/flame-kk.ui.adhoc/861/HTML_Report/

Repro Steps:
1) Update phone to 20150813030210
2) Open Messages
3) Attempt to send a message.

Actual:
Sending fails due to lack of data connection.

Expected:

Data connection is present and calls/messages can be sent.


Traceback from test_sms_notification.py (most recent call last):

File "/var/jenkins/1/workspace/flame-kk-319.mozilla-central.nightly.ui.functional.non-smoke.unstable/.env/local/lib/python2.7/site-packages/marionette_client-0.16-py2.7.egg/marionette/marionette_test.py", line 296, in run
testMethod()
File "/var/jenkins/1/workspace/flame-kk-319.mozilla-central.nightly.ui.functional.non-smoke.unstable/tests/python/gaia-ui-tests/gaiatest/tests/functional/messages/test_sms_notification.py", line 22, in test_sms_notification
self.data_layer.send_sms(self.environment.phone_numbers[0], _text_message_content, skip_verification=True)
IndexError: list index out of range
 

Environmental Variables:

Device firmware (base)     L1TC000118D0
Device firmware (date)     13 Aug 2015 10:21:15
Device firmware (incremental)     eng.cltbld.20150813.062106
Device firmware (release)     4.4.2
Device identifier     flame
Device memory     219772 kB
Device serial     e47cd89b
Device uptime     0 days 0 hours 2 minutes 10 seconds
Gaia date     12 Aug 2015 16:40:43
Gaia revision     52f3ea58df38
Gecko build     20150813030210
Gecko revision     7649ffe28b67aa2dad0f67ea01500c0ff91b2bac
Gecko version     43.0a1

Reproducible manually: No

Repro frequency: 5/5

Comment 1

[Martijn Wargers (dead)]

I guess the contract with the provider is expired or something regarding that sim card?

Comment 2

[No-Jun Park [:njpark]]

Since the test result looks like it's non-bitbar setup, I'm speculating that we didn't account for those sim cards last time we were checking the number of active sim cards that we held.  Best thing would be to check them in person.  Perhaps pallavi might be able to help out?

Comment 3

[Martijn Wargers (dead)]

Pallavi, could you perhaps find out?

Comment 4

[Pallavi Yaramada :pallavi]

Which devices are these? What's the device #?
Are they In the MTV Lab?

I have 5 SIM cards with IT ready to be put in the MTV phones. 
I can put them in on Monday.

Comment 5

[Nicholas Nelson [:NicholasN]]

These are flame devices in the MTV lab.

It looks like this error was encountered on device b2g-16.1, which was on the non-smoke unstable run.

The other devices used yesterday did not hit this issue, but may be worth checking. They are: b2g-20.1 (on the unstable smoke run), b2g-21.1`(on non-smoke 1), and b2g-20.2 (on non-smoke 2).

Comment 6

[Martijn Wargers (dead)]

(In reply to Nicholas Nelson [:NicholasN] from comment #5)
> It looks like this error was encountered on device b2g-16.1, which was on
> the non-smoke unstable run.

That makes use of this .json file, right Johan? https://github.com/mozilla/webqa-credentials/blob/master/b2g/b2g-16.1.json
That doesn't even contain phone numbers. Why is that one being used for phone related tests then? Apparently, the device has a sim, because the screenshot shows that the device does try to connect to a mobile provider.

Comment 7

[Johan Lorenzo [:jlorenzo]]

My bad, I changed b2g-16.1 in bug 1188327, and I put the UI label to that Jenkins node[1]. I removed that node from the UI list, so this device shouldn't run the smoke or non smoke suite anymore. 

[1] http://jenkins1.qa.scl3.mozilla.com/computer/b2g-16.1/