Closed Bug 1048138 Opened 10 years ago Closed 10 years ago

Re-enable notification marionnette tests

Categories

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

ARM
Gonk (Firefox OS)
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED
2.1 S3 (29aug)

People

(Reporter: gerard-majax, Assigned: gerard-majax)

References

Details

(Whiteboard: [systemsfe])

Attachments

(2 files, 1 obsolete file)

46 bytes, text/x-github-pull-request
Details | Review
84 bytes, text/plain
Details
Those tests have been disabled because of some intermittences when turning on Gaia-Try on TPBL. But we cannot live without them!
Assignee: nobody → lissyx+mozillians
Attached file Gaia PR
Attached file Gaia-Try (obsolete) —
(In reply to Alexandre LISSY :gerard-majax from comment #2)
> Created attachment 8466921 [details]
> Gaia-Try

So that's fun: there is a lot of similar failures, but it's on other tests. Our tests seems to be green.
Attached file Gaia-Try
This is a new Gaia-Try
Attachment #8466921 - Attachment is obsolete: true
Okay so I can reproduce the issue locally. After the fifth run:

  Desktop Notifications
    ✓ should be cleared after opening app (9458ms)

  Notification events
    ✓ click event starts application (4867ms)
    ✓ close event removes notification (5120ms)
    ✓ closing notification invokes close handler (2736ms)
    ✓ click event on resent notification starts application (5462ms)
    ✓ close event removes resent notification (5952ms)

  Notification.get():
    ✓ promise is fulfilled 
    ✓ promise returns a new notification 
    ✓ get works with tag option 
    1) "before each" hook

  9 passing (1m)
  1 failing

  1) Notification.get(): "before each" hook:
     Uncaught 
  Error: Polling socket recv() timeout!
      at TcpSync._readResponse (/home/alex/codaz/Mozilla/b2g/gaia/node_modules/marionette-client/lib/marionette/drivers/tcp-sync.js:140:30)
      at TcpSync.send (/home/alex/codaz/Mozilla/b2g/gaia/node_modules/marionette-client/lib/marionette/drivers/tcp-sync.js:153:24)
      at Object.send (/home/alex/codaz/Mozilla/b2g/gaia/node_modules/marionette-client/lib/marionette/client.js:457:36)
      at Object._newSession (/home/alex/codaz/Mozilla/b2g/gaia/node_modules/marionette-client/lib/marionette/client.js:549:19)
      at /home/alex/codaz/Mozilla/b2g/gaia/node_modules/marionette-client/lib/marionette/client.js:735:14
      at Object.<anonymous> (/home/alex/codaz/Mozilla/b2g/gaia/node_modules/marionette-client/lib/marionette/client.js:529:11)
      at Object.Client._handleCallback (/home/alex/codaz/Mozilla/b2g/gaia/node_modules/marionette-client/lib/marionette/client.js:484:23)
      at /home/alex/codaz/Mozilla/b2g/gaia/node_modules/marionette-client/lib/marionette/client.js:510:21
      at TcpSync.send (/home/alex/codaz/Mozilla/b2g/gaia/node_modules/marionette-client/lib/marionette/drivers/tcp-sync.js:153:10)
      at Object.send (/home/alex/codaz/Mozilla/b2g/gaia/node_modules/marionette-client/lib/marionette/client.js:457:36)
      at Object.Client._sendCommand (/home/alex/codaz/Mozilla/b2g/gaia/node_modules/marionette-client/lib/marionette/client.js:503:19)
      at Object._getActorId (/home/alex/codaz/Mozilla/b2g/gaia/node_modules/marionette-client/lib/marionette/client.js:526:19)
      at Object.startSession (/home/alex/codaz/Mozilla/b2g/gaia/node_modules/marionette-client/lib/marionette/client.js:733:19)
      at /home/alex/codaz/Mozilla/b2g/gaia/node_modules/marionette-js-runner/lib/runtime/hostmanager.js:96:16
      at TcpSync.<anonymous> (/home/alex/codaz/Mozilla/b2g/gaia/node_modules/marionette-client/lib/marionette/drivers/tcp-sync.js:112:7)
      at process._tickCallback (node.js:419:13)



make: *** [test-integration-test] Erreur 1
I'm wondering if it could not be blocked by bug 1037924.
Depends on: 1037924
(In reply to Alexandre LISSY :gerard-majax from comment #6)
> I'm wondering if it could not be blocked by bug 1037924.

Looking at the output of your try run I think you are correct. I didn't see the notifications test fail outside of that issue. You can go ahead and land if you want, R=kgrandon if desired.
I don't think there is any rush to land this. Given the intermittent rate in gaia-try [1], I don't think having this test enabled gives us any useful info to prevent regressions.

1.) https://tbpl.mozilla.org/?rev=068b7106b35596577e71b6f841b9d3cdf72abbc3&tree=Gaia-Try
(In reply to Michael Henretty [:mhenretty] from comment #8)
> I don't think there is any rush to land this. Given the intermittent rate in
> gaia-try [1], I don't think having this test enabled gives us any useful
> info to prevent regressions.
> 
> 1.)
> https://tbpl.mozilla.org/
> ?rev=068b7106b35596577e71b6f841b9d3cdf72abbc3&tree=Gaia-Try

Sure, but a perma-fail is still fairly easy to identify. If we can re-enable the test and it's not failing I think it makes sense to do so.

Solving bug 1037924 should absolutely be our highest priority though.
Blocks: 1035939
No longer depends on: 1037924
Target Milestone: 2.1 S2 (15aug) → 2.1 S3 (29aug)
(In reply to Michael Henretty [:mhenretty] from comment #10)
> Gaia-Try for notification.get tests:
> https://tbpl.mozilla.org/
> ?rev=373b169fe6ea337df9250c1e8a7c74107d3de759&tree=Gaia-Try
> 
> Gaia-Try for mozResend tests:
> https://tbpl.mozilla.org/
> ?rev=cdc73087993ae3da7499b443140e565e074a7aa4&tree=Gaia-Try

Still lots of red :(
It appears this was landed when we had a perma-failure. You should be good to rebase this and try again, but it appears that notification_resend_test.js might still be failing.
Looks like resend notifications is perma-red. But notification.get tests are probably ready to be re-enabled.
Depends on: 1010415
All dependencies resolved, all notification tests re-enabled. Closing.
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: