Oliver Nelson [:oliverthor] Reporter
	Description • 9 years ago

Description:
test_sms_notification.py is failing consistently after sending an sms to the same device. The test does not appear to be receiving notifications when performed via Jenkins, however these notifications are observed when performed via local automation and when performed manually.

Issue appears identical to that described in:
* https://bugzilla.mozilla.org/show_bug.cgi?id=1172460

* http://jenkins1.qa.scl3.mozilla.com/job/flame-kk.ui.adhoc.bitbar/78/HTML_Report/

Repro Steps:
1) Update phone to 20150608010204
-- this all appears to be done in the background by automation --
2) Open the Messages app
3) Compose new message
4) Enter address for message as the same phone
5) Enter any text for field, send to phone and return to home
-- outside sending message --
6) Observe message notification

Actual [over Jenkins]:
No notification is observed

Expected: 
Message toast is observed from top of phone


Traceback (most recent call last):
File "/var/lib/jenkins/jobs/flame-kk.ui.adhoc.bitbar/workspace/.env/lib/python2.7/site-packages/marionette_client-0.13-py2.7.egg/marionette/marionette_test.py", line 296, in run
testMethod()
File "/var/lib/jenkins/jobs/flame-kk.ui.adhoc.bitbar/workspace/tests/python/gaia-ui-tests/gaiatest/tests/functional/messages/test_sms_notification.py", line 26, in test_sms_notification
message="Notification did not appear. SMS database dump: %s " % self.data_layer.get_all_sms())
File "/var/lib/jenkins/jobs/flame-kk.ui.adhoc.bitbar/workspace/tests/python/gaia-ui-tests/gaiatest/apps/system/app.py", line 41, in wait_for_notification_toaster_displayed
Wait(self.marionette, timeout).until(expected.element_displayed(el), message=message)
File "/var/lib/jenkins/jobs/flame-kk.ui.adhoc.bitbar/workspace/.env/lib/python2.7/site-packages/marionette_driver-0.7-py2.7.egg/marionette_driver/wait.py", line 143, in until
cause=last_exc)
TimeoutException: TimeoutException: Timed out after 300.1 seconds with message: Notification did not appear. SMS database dump: [{u'body': u'Automated Test 1433786247.76', u'deliveryStatus': u'not-applicable', u'sender': u'16506031378', u'read': True, u'timestamp': 1433786246436, u'threadId': 1, u'sentTimestamp': 1433786248090, u'delivery': u'sent', u'receiver': u'+16509605939', u'iccId': u'89014103277804619059', u'type': u'sms', u'id': 1, u'deliveryTimestamp': 0, u'messageClass': u'normal'}] 


Environment Variables:
Device firmware (base) 	L1TC100118D0
Device firmware (date) 	08 Jun 2015 08:35:05
Device firmware (incremental) 	eng.cltbld.20150608.043454
Device firmware (release) 	4.4.2
Device identifier 	flame
Device memory 	219772 kB
Device serial 	f0314099
Device uptime 	0 days 0 hours 2 minutes 8 seconds
Gaia date 	05 Jun 2015 17:55:07
Gaia revision 	1d62b3240856
Gecko build 	20150608010204
Gecko revision 	7d4ab4a9febd
Gecko version 	41.0a1


Reproducible manually: No

Repro frequency: 
* 0/5 passing via Jenkins
* 5/5 passing via local automation or manual

	Martijn Wargers (dead)
	Comment 1 • 9 years ago

(In reply to Oliver Nelson [:oliverthor] from comment #0)
> Issue appears identical to that described in:
> * https://bugzilla.mozilla.org/show_bug.cgi?id=1172460

Well, the difference here is that in this case the sms hasn't been received at all. It doesn't show up in the database dump and the screenshot doesn't show the blue line (notification line or whatever it's called) that makes it clear an sms was received.

The issue here seems to be that the sender and receiver phone numbers are different. 
So I thin that means there is something wrong in the testvars.json file of this particular bitbar instance.
Dave Hunt, I guess that means I should write a mail to bitbar support for this, right?

	Dave Hunt [:davehunt] [he/him] ⌚BST
	Comment 2 • 9 years ago

Hmm.. I distinctly recall responding to this - maybe I forgot to click save! Does that affect more than one device? If so, it's likely an environment issue. If not, it may be that the phone number label is incorrect on Bitbar's side. You can find the phone number associated with the selected in the device.json artifact in Jenkins. We should e-mail Bitbar if we think the wrong phone number is associated with a device.

	Martijn Wargers (dead)
	Comment 3 • 9 years ago

From bug 1172460, comment 15:
"
This issue is still failing: it has about a 60% repro rate so it has dodged some reports.
"

I think it would be good to have some logging in regarding the phone numbers to more easily see when something like this is going wrong.

	Martijn Wargers (dead)
	Comment 6 • 9 years ago

(In reply to Autolander from comment #5)
> Created attachment 8640582 [details] [review]
> [gaia] mwargers:1172618_unstable > mozilla-b2g:master

Added stable = false to this test: https://github.com/mozilla-b2g/gaia/commit/27db84a9ea5777a09c2184458acc2908e140cba3

	BMO Automation
	Comment 7 • 6 years ago

Firefox OS is not being worked on