Closed Bug 1236446 Opened 10 years ago Closed 10 years ago

Intermittent new_activity_test.js | Messages as "new" activity target Send new message Activity with "body" only

Categories

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

Product:
Firefox OS Graveyard
Component:
Gaia::SMS
Platform:
ARM
Gonk (Firefox OS)
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED DUPLICATE of bug 1236248

People

(Reporter: nigelb, Unassigned)

References

(
URL
)

Details

(Keywords: intermittent-failure)

https://treeherder.mozilla.org/logviewer.html#?job_id=6409229&repo=fx-team 09:47:51 INFO - TEST-START | apps/sms/test/marionette/new_activity_test.js | Messages as "new" activity target Send new message Activity with "body" only 09:49:05 INFO - TEST-UNEXPECTED-FAIL | apps/sms/test/marionette/new_activity_test.js | Messages as "new" activity target Send new message Activity with "body" only 09:49:05 INFO - Crash detected but error running stackwalk 09:49:05 INFO - TEST-END | apps/sms/test/marionette/new_activity_test.js | Messages as "new" activity target Send new message Activity with "body" only took 61547 ms 09:49:05 INFO - TEST-START | apps/sms/test/marionette/new_activity_test.js | Messages as "new" activity target Send new message Activity with "body" and unknown "number" 09:49:20 INFO - TEST-PASS | apps/sms/test/marionette/new_activity_test.js | Messages as "new" activity target Send new message Activity with "body" and unknown "number" 09:49:20 INFO - TEST-END | apps/sms/test/marionette/new_activity_test.js | Messages as "new" activity target Send new message Activity with "body" and unknown "number" took 2743 ms 09:49:20 INFO - TEST-START | apps/sms/test/marionette/new_activity_test.js | Messages as "new" activity target Send new message Activity with "body" and contact "number" 09:49:36 INFO - TEST-PASS | apps/sms/test/marionette/new_activity_test.js | Messages as "new" activity target Send new message Activity with "body" and contact "number" 09:49:36 INFO - TEST-END | apps/sms/test/marionette/new_activity_test.js | Messages as "new" activity target Send new message Activity with "body" and contact "number" took 2674 ms 09:49:36 INFO - TEST-START | apps/sms/test/marionette/new_activity_test.js | Messages as "new" activity target Send new message Activity with thread "number" 09:49:51 INFO - TEST-PASS | apps/sms/test/marionette/new_activity_test.js | Messages as "new" activity target Send new message Activity with thread "number" 09:49:51 INFO - TEST-END | apps/sms/test/marionette/new_activity_test.js | Messages as "new" activity target Send new message Activity with thread "number" took 3122 ms 09:49:51 INFO - TEST-START | apps/sms/test/marionette/new_activity_test.js | Messages as "new" activity target Send new message Activity with thread "number" and "body" 09:50:06 INFO - TEST-PASS | apps/sms/test/marionette/new_activity_test.js | Messages as "new" activity target Send new message Activity with thread "number" and "body" 09:50:06 INFO - TEST-END | apps/sms/test/marionette/new_activity_test.js | Messages as "new" activity target Send new message Activity with thread "number" and "body" took 3183 ms 09:50:11 INFO - TEST-START | apps/sms/test/marionette/notification_test.js | Message notification tests Run application via notification when "notification" system message is generated 09:50:24 INFO - TEST-PASS | apps/sms/test/marionette/notification_test.js | Message notification tests Run application via notification when "notification" system message is generated 09:50:24 INFO - TEST-END | apps/sms/test/marionette/notification_test.js | Message notification tests Run application via notification when "notification" system message is generated took 2558 ms 09:50:24 INFO - TEST-START | apps/sms/test/marionette/notification_test.js | Message notification tests Run application via notification when user taps on notification in Utility tray 09:50:54 INFO - TEST-PASS | apps/sms/test/marionette/notification_test.js | Message notification tests Run application via notification when user taps on notification in Utility tray 09:50:54 INFO - TEST-END | apps/sms/test/marionette/notification_test.js | Message notification tests Run application via notification when user taps on notification in Utility tray took 20892 ms 09:50:55 INFO - TEST-START | apps/sms/test/marionette/notification_test.js | Message notification tests Run application via notification when user removes notification from Utility tray 09:51:28 INFO - TEST-PASS | apps/sms/test/marionette/notification_test.js | Message notification tests Run application via notification when user removes notification from Utility tray 09:51:28 INFO - TEST-END | apps/sms/test/marionette/notification_test.js | Message notification tests Run application via notification when user removes notification from Utility tray took 23085 ms 09:51:28 INFO - TEST-START | apps/sms/test/marionette/notification_test.js | Message notification tests Display a conversation from a notification Clicking a notification while a conversation is loading 09:51:45 INFO - TEST-PASS | apps/sms/test/marionette/notification_test.js | Message notification tests Display a conversation from a notification Clicking a notification while a conversation is loading 09:51:46 INFO - TEST-END | apps/sms/test/marionette/notification_test.js | Message notification tests Display a conversation from a notification Clicking a notification while a conversation is loading took 6272 ms 09:51:51 INFO - TEST-START | apps/sms/test/marionette/phone_number_service_test.js | mozPhoneNumberService: test fuzzy matches 09:52:04 INFO - TEST-PASS | apps/sms/test/marionette/phone_number_service_test.js | mozPhoneNumberService: test fuzzy matches 09:52:04 INFO - TEST-END | apps/sms/test/marionette/phone_number_service_test.js | mozPhoneNumberService: test fuzzy matches took 24 ms 09:52:04 INFO - *~*~* Results *~*~* 09:52:04 INFO - passed: 49 09:52:04 INFO - failed: 1 09:52:04 INFO - todo: 0 09:52:04 INFO - 49 passing (24m) 09:52:04 INFO - 1 failing 09:52:04 INFO - 1) Messages as "new" activity target Send new message Activity with "body" only: 09:52:04 INFO - + expected - actual 09:52:04 INFO - rash detected but error running stackwalk 09:52:04 INFO - npm ERR! Linux 3.13.0-48-generic 09:52:04 INFO - npm ERR! argv "/usr/local/bin/node" "/usr/local/bin/npm" "run" "marionette" "--" "--buildapp=desktop" "--reporter=mocha-tbpl-reporter" "--marionette-capabilities=/home/worker/gaia/tests/jsmarionette/capabilities.json" 09:52:04 INFO - npm ERR! node v4.2.2 09:52:04 INFO - npm ERR! npm v2.14.7 09:52:04 INFO - npm ERR! code ELIFECYCLE 09:52:04 INFO - npm ERR! gaia@0.0.3 marionette: `gaia-marionette "--buildapp=desktop" "--reporter=mocha-tbpl-reporter" "--marionette-capabilities=/home/worker/gaia/tests/jsmarionette/capabilities.json"` 09:52:04 INFO - npm ERR! Exit status 1 09:52:04 INFO - npm ERR! 09:52:04 INFO - npm ERR! Failed at the gaia@0.0.3 marionette script 'gaia-marionette "--buildapp=desktop" "--reporter=mocha-tbpl-reporter" "--marionette-capabilities=/home/worker/gaia/tests/jsmarionette/capabilities.json"'. 09:52:04 INFO - npm ERR! This is most likely a problem with the gaia package, 09:52:04 INFO - npm ERR! not with npm itself. 09:52:04 INFO - npm ERR! Tell the author that this fails on your system: 09:52:04 INFO - npm ERR! gaia-marionette "--buildapp=desktop" "--reporter=mocha-tbpl-reporter" "--marionette-capabilities=/home/worker/gaia/tests/jsmarionette/capabilities.json" 09:52:04 INFO - npm ERR! You can get their info via: 09:52:04 INFO - npm ERR! npm owner ls gaia 09:52:04 INFO - npm ERR! There is likely additional logging output above. 09:52:04 INFO - npm ERR! Please include the following file with any support request: 09:52:04 INFO - npm ERR! /home/worker/gaia/npm-debug.log 09:52:04 INFO - make: *** [test-integration-test] Error 1 09:52:04 ERROR - Return code: 2 09:52:04 INFO - TinderboxPrint: gaia-integration-tests: 49/<em class="testfail">1</em>/0 09:52:04 ERROR - Tests exited with return code 2: harness failures 09:52:04 ERROR - # TBPL FAILURE # 09:52:04 WARNING - setting return code to 2
See Also: → 1235842
Test is disabled, so investigation and fix for all new_activity intermittents can be done in single bug.
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.