Closed Bug 1168363 Opened 9 years ago Closed 8 years ago

Intermittent activity_action_menu_test.js | activity action menu test works after opening an app

Categories

(Firefox OS Graveyard :: Gaia, defect)

ARM
Gonk (Firefox OS)
defect
Not set
normal

Tracking

(b2g-v2.2 affected)

RESOLVED FIXED
2.6 S5 - 1/15
Tracking Status
b2g-v2.2 --- affected

People

(Reporter: RyanVM, Assigned: apastor)

References

Details

(Keywords: intermittent-failure)

Attachments

(2 files)

20:35:41 INFO - TEST-START | apps/system/test/marionette/activity_action_menu_test.js | activity action menu test works after opening an app
20:35:41 INFO - TEST-UNEXPECTED-FAIL | apps/system/test/marionette/activity_action_menu_test.js | activity action menu test works after opening an app
20:35:41 INFO - NoSuchElement: (7) Unable to locate element: #screen > form.visible
20:35:41 INFO - Remote Stack:
20:35:41 INFO - <none>
20:35:41 INFO - at Error.MarionetteError (/builds/slave/test/gaia/node_modules/marionette-client/lib/marionette/error.js:66:13)
20:35:41 INFO - at Object.Client._handleCallback (/builds/slave/test/gaia/node_modules/marionette-client/lib/marionette/client.js:481:19)
20:35:41 INFO - at /builds/slave/test/gaia/node_modules/marionette-client/lib/marionette/client.js:516:23
20:35:41 INFO - at TcpSync.send (/builds/slave/test/gaia/node_modules/marionette-client/lib/marionette/drivers/tcp-sync.js:159:10)
20:35:41 INFO - at Object.send (/builds/slave/test/gaia/node_modules/marionette-client/lib/marionette/client.js:459:36)
20:35:41 INFO - at Object.Client._sendCommand (/builds/slave/test/gaia/node_modules/marionette-client/lib/marionette/client.js:509:21)
20:35:41 INFO - at Object._findElement (/builds/slave/test/gaia/node_modules/marionette-client/lib/marionette/client.js:1314:19)
20:35:41 INFO - at Object.findElement (/builds/slave/test/gaia/node_modules/marionette-client/lib/marionette/client.js:1366:32)
20:35:41 INFO - at Object.MarionetteHelper.waitForElement (/builds/slave/test/gaia/node_modules/marionette-helper/index.js:139:19)
20:35:41 INFO - at Object.System.waitForActivityMenu (/builds/slave/test/gaia/apps/system/test/marionette/lib/system.js:426:35)
20:35:41 INFO - at Context.<anonymous> (/builds/slave/test/gaia/apps/system/test/marionette/activity_action_menu_test.js:33:14)
20:35:41 INFO - at callFn (/builds/slave/test/gaia/node_modules/mocha/lib/runnable.js:223:21)
20:35:41 INFO - at Test.Runnable.run (/builds/slave/test/gaia/node_modules/mocha/lib/runnable.js:216:7)
20:35:41 INFO - at Runner.runTest (/builds/slave/test/gaia/node_modules/mocha/lib/runner.js:373:10)
20:35:41 INFO - at /builds/slave/test/gaia/node_modules/mocha/lib/runner.js:451:12
20:35:41 INFO - at next (/builds/slave/test/gaia/node_modules/mocha/lib/runner.js:298:14)
20:35:41 INFO - at /builds/slave/test/gaia/node_modules/mocha/lib/runner.js:308:7
20:35:41 INFO - at next (/builds/slave/test/gaia/node_modules/mocha/lib/runner.js:246:23)
20:35:41 INFO - at /builds/slave/test/gaia/node_modules/mocha/lib/runner.js:270:7
20:35:41 INFO - at done (/builds/slave/test/gaia/node_modules/mocha/lib/runnable.js:185:5)
20:35:41 INFO - at callFn (/builds/slave/test/gaia/node_modules/mocha/lib/runnable.js:228:7)
20:35:41 INFO - at Hook.Runnable.run (/builds/slave/test/gaia/node_modules/mocha/lib/runnable.js:216:7)
20:35:41 INFO - at next (/builds/slave/test/gaia/node_modules/mocha/lib/runner.js:258:10)
20:35:41 INFO - at /builds/slave/test/gaia/node_modules/mocha/lib/runner.js:270:7
20:35:41 INFO - at done (/builds/slave/test/gaia/node_modules/mocha/lib/runnable.js:185:5)
20:35:41 INFO - at /builds/slave/test/gaia/node_modules/mocha/lib/runnable.js:199:9
20:35:41 INFO - at Object.executeHook (/builds/slave/test/gaia/node_modules/marionette-client/lib/marionette/client.js:371:18)
20:35:41 INFO - at process._tickCallback (node.js:415:13)
20:35:41 INFO - TEST-END | apps/system/test/marionette/activity_action_menu_test.js | activity action menu test works after opening an app took 31861 ms
This is basically permafailing across the trees at the moment.
Flags: needinfo?(aus)
In case anyone was wondering what is *supposed* to happen here, someone is supposed to disable this test, before you lose visibility of the entire chunk of the suite over this one test failing.
(In reply to Phil Ringnalda (:philor) from comment #429)
> In case anyone was wondering what is *supposed* to happen here, someone is
> supposed to disable this test, before you lose visibility of the entire
> chunk of the suite over this one test failing.

Thanks. I'll go ahead and disable this so we don't have to do that.
I think a [test disabled] in the whiteboard is what Orange Factor looks for to show it greyed-out and not in need of yelling :)
Whiteboard: [test disabled]
Flags: needinfo?(aus)
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → FIXED
Tim, can you please look into this recent spike or suggest someone who can?
Flags: needinfo?(timdream)
Whiteboard: [test disabled]
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Julien, would you mind take a look? It fails at line 28 which is:

      messagesApp.Inbox.navigateToComposer();

https://treeherder.mozilla.org/logviewer.html#?repo=fx-team&job_id=4428090
Flags: needinfo?(timdream) → needinfo?(felash)
Specifically, this timed out

  get createNewMessageButton() {
    return this.client.helper.waitForElement(
      SELECTORS.navigateToComposerHeaderButton
    );
  },

from

  // Temporary solution to keep the current tests running.
  // TODO: bug 1167103
  navigateToComposer: function() {
    this.createNewMessageButton.tap();
  }

at 

gaia/apps/sms/test/marionette/lib/views/inbox/accessors.js:52:9
From the log, when opening the screenshot, I have a white screen, which implies that the app does not load properly. That's likely why the button is not found. I'd like to see the Gecko logs as well :/

However, when running locally, it passes this line but fails at the next line:

  system.waitForKeyboard();


I don't know why we have a difference between my local environment and treeherder.

So I can't really debug...


Maybe we can wait that https://treeherder.mozilla.org/#/jobs?repo=gaia-master is fixed by aus, and try to reproduce there; we have gecko output on these jobs.

And maybe we can ask to enable gecko output on the other jobs as well. NI aus for this last comment.
Flags: needinfo?(felash) → needinfo?(aus)
The "gaia-master" repository in Treeherder is still broken; so I created a PR to trigger a build for master so that I can see if I reproduce the issue and look at gecko logs.
Here is a failing task with gecko logs: https://tools.taskcluster.net/task-inspector/#ME_1hXm7Tu-xkIWYGP7fFQ/0

But no clue :/
(In reply to Julien Wajsberg [:julienw] (PTO Sept 2nd -> Sept 9th) from comment #612)
> Here is a failing task with gecko logs:
> https://tools.taskcluster.net/task-inspector/#ME_1hXm7Tu-xkIWYGP7fFQ/0
> 
> But no clue :/

Hi Julien, the gecko logs should be available for all jobs but since gaia-master isn't running using a PR is probably the best way to get them.
Flags: needinfo?(aus)
Assignee: nobody → apastor
Target Milestone: --- → 2.6 S5 - 1/15
Attachment #8706255 - Flags: review?(mhenretty)
Comment on attachment 8706255 [details] [review]
[gaia] albertopq:1168363-action-menu-test > mozilla-b2g:master

Excelente!!
Attachment #8706255 - Flags: review?(mhenretty) → review+
master: https://github.com/mozilla-b2g/gaia/commit/180f43640f3076a56643cd87b0b6a82c01147811
Status: REOPENED → RESOLVED
Closed: 9 years ago8 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: