Closed Bug 1189882 Opened 9 years ago Closed 6 years ago

Intermittent tests/jsmarionette/plugins/marionette-apps/test/app_test.js | App #launch should launch the appropriate app

Categories

(Firefox OS Graveyard :: Gaia, defect)

All
Gonk (Firefox OS)
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED WONTFIX

People

(Reporter: RyanVM, Unassigned)

Details

(Keywords: intermittent-failure)

Attachments

(2 files)

      No description provided.
Gareth or Aus, can you please help us look at this test? I think there is an actual problem with client.apps.launch, as I've seen this fail intermittent in a lot of different tests. I've disabled a bunch on those but I am hesitant to disable this one because I think there is a systemic issue here that is causing us a lot of problems in Gij.
Blocks: 1222215
Flags: needinfo?(gaye)
Flags: needinfo?(aus)
Here's an instance where launch is timing out [1]. FWIW, it could be that we just need to increase the waitFor timeout inside launch.

1.) https://bugzilla.mozilla.org/show_bug.cgi?id=1233533
I'll put this on top of my list. Will let Gareth chime in as well.
Assignee: nobody → aus
Flags: needinfo?(aus)
Status: NEW → ASSIGNED
I don't think we need this anymore since app.launch now waits for system to be fully loaded rather than the homscreen being displayed. Let's remove the dependency and disable this test.

disabled in master: https://github.com/mozilla-b2g/gaia/commit/04c2822c7c25ce091b99d9a05b8ac457226ee2e8
No longer blocks: 1222215
Flags: needinfo?(gaye)
The original issue was fixed, but I found something else that could easily manifest itself in the same way. I have a pull request up that solves the issue.
Attachment #8705450 - Flags: review?(mhenretty)
Commit (master): https://github.com/mozilla-b2g/gaia/commit/15309984bc5454d8cce463264f0e851e3c7f2d68

Fixed!

Test re-enabled as well!
Status: ASSIGNED → RESOLVED
Closed: 8 years ago
Resolution: --- → FIXED
https://treeherder.mozilla.org/#/jobs?repo=b2g-inbound&revision=c4ac356746c1&filter-searchStr=6f8476efbe56be16479afce1289a8eda03fcd4fa

Not sure how that 20% failure rate compares to what it was before, but it's too much, please revert the reenabling.
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Ah ha, I think I know what's wrong with it, but, it was 100% green on gaia before I pushed. Which is annoying. The instance sizes must be different between gaia and b2g-inbound which is why it didn't show up for me.

I've re-disabled the test for now and will have a follow up pull request to address the failure issue we're seeing in b2g-inbound but not in gaia tomorrow.

commit (master): https://github.com/mozilla-b2g/gaia/commit/0e6160a58b41b48a8e4bb75ab9e722d9491251f4 -- for disabled test.
Assignee: aus → nobody
Firefox OS is not being worked on
Status: REOPENED → RESOLVED
Closed: 8 years ago6 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: