Closed Bug 1037500 Opened 10 years ago Closed 10 years ago

Clock test fails from script timeout, preventing results from appearing in Datazilla

Categories

(Firefox OS Graveyard :: Gaia::PerformanceTest, defect, P1)

ARM
Gonk (Firefox OS)
defect

Tracking

(b2g-v2.0 fixed, b2g-v2.1 fixed)

RESOLVED FIXED
2.1 S1 (1aug)
Tracking Status
b2g-v2.0 --- fixed
b2g-v2.1 --- fixed

People

(Reporter: Eli, Assigned: Eli)

References

Details

(Keywords: perf, Whiteboard: [c=automation p=2 s= u=])

Attachments

(1 file)

The Clock test is not showing any results on Datazilla. After digging into the logs in Jenkins it appears that there is a socket timeout occurring which errors the tests for the Clock.

Logs:
=====

ScriptTimeout',
  stack: 'ScriptTimeout: (28) timed out
  Remote Stack:
	<none>
    at Error.MarionetteError (/var/jenkins/1/workspace/flame.b2g-inbound.perf.gaia/node_modules/marionette-client/lib/marionette/error.js:67:13)
    at Object.Client._handleCallback (/var/jenkins/1/workspace/flame.b2g-inbound.perf.gaia/node_modules/marionette-client/lib/marionette/client.js:476:19)
    at /var/jenkins/1/workspace/flame.b2g-inbound.perf.gaia/node_modules/marionette-client/lib/marionette/client.js:510:21
    at TcpSync.send (/var/jenkins/1/workspace/flame.b2g-inbound.perf.gaia/node_modules/marionette-client/lib/marionette/drivers/tcp-sync.js:100:10)
    at Object.send (/var/jenkins/1/workspace/flame.b2g-inbound.perf.gaia/node_modules/marionette-client/lib/marionette/client.js:457:36)
    at Object.Client._sendCommand (/var/jenkins/1/workspace/flame.b2g-inbound.perf.gaia/node_modules/marionette-client/lib/marionette/client.js:503:19)
    at Object._executeScript (/var/jenkins/1/workspace/flame.b2g-inbound.perf.gaia/node_modules/marionette-client/lib/marionette/client.js:1468:19)
    at Object.executeAsyncScript (/var/jenkins/1/workspace/flame.b2g-inbound.perf.gaia/node_modules/marionette-client/lib/marionette/client.js:1249:19)
    at Object.PerfTestApp.waitForPerfEvents (/var/jenkins/1/workspace/flame.b2g-inbound.perf.gaia/tests/performance/app.js:95:17)
    at Object.PerformanceHelper.waitForPerfEvent (/var/jenkins/1/workspace/flame.b2g-inbound.perf.gaia/tests/performance/performance_helper.js:190:16)
    at /var/jenkins/1/workspace/flame.b2g-inbound.perf.gaia/tests/performance/startup_events_test.js:94:25
    at Object.PerformanceHelper.task (/var/jenkins/1/workspace/flame.b2g-inbound.perf.gaia/tests/performance/performance_helper.js:178:7)
    at /var/jenkins/1/workspace/flame.b2g-inbound.perf.gaia/tests/performance/performance_helper.js:164:16
    at Object.Client.waitForSync (/var/jenkins/1/workspace/flame.b2g-inbound.perf.gaia/node_modules/marionette-client/lib/marionette/client.js:668:18)
    at Object.Client.waitFor (/var/jenkins/1/workspace/flame.b2g-inbound.perf.gaia/node_modules/marionette-client/lib/marionette/client.js:650:60)
    at Object.Helper.delay (/var/jenkins/1/workspace/flame.b2g-inbound.perf.gaia/tests/js-marionette/helper.js:28:12)
    at Object.PerformanceHelper.delay (/var/jenkins/1/workspace/flame.b2g-inbound.perf.gaia/tests/performance/performance_helper.js:186:24)
    at trigger (/var/jenkins/1/workspace/flame.b2g-inbound.perf.gaia/tests/performance/performance_helper.js:163:14)
    at Object.PerformanceHelper.repeatWithDelay (/var/jenkins/1/workspace/flame.b2g-inbound.perf.gaia/tests/performance/performance_helper.js:168:7)
    at Context.<anonymous> (/var/jenkins/1/workspace/flame.b2g-inbound.perf.gaia/tests/performance/startup_events_test.js:89:23)
    at callFn (/var/jenkins/1/workspace/flame.b2g-inbound.perf.gaia/node_modules/mocha/lib/runnable.js:223:21)
    at Test.Runnable.run (/var/jenkins/1/workspace/flame.b2g-inbound.perf.gaia/node_modules/mocha/lib/runnable.js:216:7)
    at Runner.runTest (/var/jenkins/1/workspace/flame.b2g-inbound.perf.gaia/node_modules/mocha/lib/runner.js:373:10)
    at /var/jenkins/1/workspace/flame.b2g-inbound.perf.gaia/node_modules/mocha/lib/runner.js:451:12
    at next (/var/jenkins/1/workspace/flame.b2g-inbound.perf.gaia/node_modules/mocha/lib/runner.js:298:14)
    at /var/jenkins/1/workspace/flame.b2g-inbound.perf.gaia/node_modules/mocha/lib/runner.js:308:7
    at next (/var/jenkins/1/workspace/flame.b2g-inbound.perf.gaia/node_modules/mocha/lib/runner.js:246:23)
    at /var/jenkins/1/workspace/flame.b2g-inbound.perf.gaia/node_modules/mocha/lib/runner.js:270:7
    at done (/var/jenkins/1/workspace/flame.b2g-inbound.perf.gaia/node_modules/mocha/lib/runnable.js:185:5)
    at callFn (/var/jenkins/1/workspace/flame.b2g-inbound.perf.gaia/node_modules/mocha/lib/runnable.js:228:7)
    at Hook.Runnable.run (/var/jenkins/1/workspace/flame.b2g-inbound.perf.gaia/node_modules/mocha/lib/runnable.js:216:7)
    at next (/var/jenkins/1/workspace/flame.b2g-inbound.perf.gaia/node_modules/mocha/lib/runner.js:258:10)
    at /var/jenkins/1/workspace/flame.b2g-inbound.perf.gaia/node_modules/mocha/lib/runner.js:270:7
    at done (/var/jenkins/1/workspace/flame.b2g-inbound.perf.gaia/node_modules/mocha/lib/runnable.js:185:5)
    at /var/jenkins/1/workspace/flame.b2g-inbound.perf.gaia/node_modules/mocha/lib/runnable.js:199:9
    at Object.executeHook (/var/jenkins/1/workspace/flame.b2g-inbound.perf.gaia/node_modules/marionette-client/lib/marionette/client.js:369:18)
    at process._tickCallback (node.js:419:13)
Summary: Clock test fails from socket timeout, preventing results from appearing in Datazilla → Clock test fails from timeout, preventing results from appearing in Datazilla
It is a script timeout.
Summary: Clock test fails from timeout, preventing results from appearing in Datazilla → Clock test fails from script timeout, preventing results from appearing in Datazilla
Blocks: 1026646
I tried a quick gaia bisect on that, and even before, when I know this worked, I get the regression. *sigh*
I am going to take this one and try to do some investigation.
Assignee: nobody → eperelman
Status: NEW → ASSIGNED
Whiteboard: [c=automation p= s= u=] → [c=automation p=2 s= u=]
It actually never worked after implementing bug 1015386

commit
19b93abbe61c1f0a5941cd4ccbd125b9bfd520c1

Even with an alarm created.
This patch adds the performance helper script back to the Clock app so we can run performance tests against it without timeouts. I've verified this patch locally using `APP=clock RUNS=30 make test-perf` and it runs perfectly.
Attachment #8464319 - Flags: review?(m)
Attachment #8464319 - Flags: review?(m) → review+
Keywords: checkin-needed
master: https://github.com/mozilla-b2g/gaia/commit/abd97f96f8c4631aff3238a917510151e1bc3a5b
Status: ASSIGNED → RESOLVED
Closed: 10 years ago
Keywords: checkin-needed
Resolution: --- → FIXED
Target Milestone: --- → 2.1 S1 (1aug)
Requesting uplift to 2.0 as the original implementation has already landed on 2.0 and is non-functional without this patch. These are important for meeting our release performance acceptance criteria.

[Feature/regressing bug #]: bug 1015386
[User impact if declined]: none
[Describe test coverage new/current, TBPL]: Feature only triggers events for testing, no user-facing features or tests
[Risks and why]: Low, as there are no user-perceived changes
[String/UUID change made/needed]: n/a
Comment on attachment 8464319 [details] [review]
Link to Github pull-request: https://github.com/mozilla-b2g/gaia/pull/22280

See comment 2.
Attachment #8464319 - Flags: approval-gaia-v2.0?
Apologies, see comment 7 (not 2).
Attachment #8464319 - Flags: approval-gaia-v2.0? → approval-gaia-v2.0+
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: