1144499 - Intermittent test_logshake_gonk.js | Test timed out

Wes Kocher (:KWierso) (Not reading bugmail; email directly if needed)

Reporter

Description

•

10 years ago

17:38:25 INFO - TEST-START | b2g/components/test/unit/test_logcapture.js 17:38:38 INFO - TEST-PASS | b2g/components/test/unit/test_logcapture.js | took 13111ms 17:38:40 INFO - TEST-START | b2g/components/test/unit/test_logcapture_gonk.js 17:39:47 INFO - TEST-PASS | b2g/components/test/unit/test_logcapture_gonk.js | took 66879ms 17:39:48 INFO - TEST-START | b2g/components/test/unit/test_logparser.js 17:40:08 INFO - TEST-PASS | b2g/components/test/unit/test_logparser.js | took 19772ms 17:40:10 INFO - TEST-START | b2g/components/test/unit/test_logshake.js 17:41:13 INFO - TEST-PASS | b2g/components/test/unit/test_logshake.js | took 63440ms 17:41:15 INFO - TEST-START | b2g/components/test/unit/test_logshake_gonk.js 17:46:15 WARNING - TEST-UNEXPECTED-TIMEOUT | b2g/components/test/unit/test_logshake_gonk.js | Test timed out 17:46:15 INFO - TEST-INFO took 300025ms 17:46:16 INFO - xpcshell return code: -1 17:46:23 WARNING - TEST-UNEXPECTED-FAIL | Received SIGINT (control-C), so stopped run. (Use --keep-going to keep running tests after killing one with SIGINT) 17:46:23 INFO - INFO | Result summary: 17:46:23 INFO - INFO | Passed: 8 17:46:23 WARNING - INFO | Failed: 1 17:46:23 WARNING - One or more unittests failed. 17:46:23 INFO - INFO | Todo: 0 17:46:23 INFO - INFO | Retried: 0 17:46:23 INFO - SUITE-END | took 650s 17:46:23 INFO - Traceback (most recent call last): 17:46:23 INFO - File "runtestsb2g.py", line 209, in run_remote_xpcshell 17:46:23 INFO - sys.exit(1) 17:46:23 INFO - SystemExit: 1 17:46:23 INFO - Automation Error: Exception caught while running tests 17:46:26 INFO - Return code: 1 17:46:26 INFO - Copying /builds/slave/test/build/qemu.log to /builds/slave/test/build/blobber_upload_dir/qemu.log 17:46:26 INFO - dumping logcat 17:46:26 INFO - Running command: ['cat', '/builds/slave/test/build/emulator-5554.log'] 17:46:26 INFO - Copy/paste: cat /builds/slave/test/build/emulator-5554.log 17:46:26 INFO - 03-18 00:27:42.667 I/qemu-props( 35): connected to 'boot-properties' qemud service. 17:46:26 INFO - 03-18 00:27:42.667 I/qemu-props( 35): receiving.. 17:46:26 INFO - 03-18 00:27:42.717 I/DEBUG ( 37): debuggerd: Mar 17 2015 12:29:35 17:46:26 INFO - 03-18 00:27:42.847 I/qemu-props( 35): received: dalvik.vm.heapsize=48m 17:46:26 INFO - 03-18 00:27:42.857 I/qemu-props( 35): receiving.. 17:46:26 INFO - 03-18 00:27:42.857 I/qemu-props( 35): received: qemu.sf.lcd_density=160 17:46:26 INFO - 03-18 00:27:42.897 I/qemu-props( 35): receiving.. 17:46:26 INFO - 03-18 00:27:42.897 I/qemu-props( 35): received: qemu.hw.mainkeys=1 17:46:26 INFO - 03-18 00:27:42.897 I/qemu-props( 35): receiving.. 17:46:26 INFO - 03-18 00:27:42.897 I/qemu-props( 35): received: qemu.sf.fake_camera=back 17:46:26 INFO - 03-18 00:27:42.917 I/qemu-props( 35): receiving.. 17:46:26 INFO - 03-18 00:27:42.917 I/qemu-props( 35): exiting (4 properties set).

Comment hidden (Legacy TBPL/Treeherder Robot)

Phil Ringnalda (:philor)

Updated

•

9 years ago

Summary: Intermittent test_logshake_gonk.js | Test timed out | Received SIGINT (control-C), so stopped run. (Use --keep-going to keep running tests after killing one with SIGINT) → Intermittent test_logshake_gonk.js | Test timed out

Comment hidden (Legacy TBPL/Treeherder Robot)

Ryan VanderMeulen [:RyanVM]

Comment 51

•

9 years ago

Alexandre, can you please investigate this frequent failure?

Flags: needinfo?(lissyx+mozillians)

:gerard-majax

Assignee

Comment 52

•

9 years ago

James, can it be related to your recent landing?

Flags: needinfo?(lissyx+mozillians) → needinfo?(hobinjk)

James Hobin [:hobinjk]

Comment 53

•

9 years ago

(In reply to Alexandre LISSY :gerard-majax from comment #52) > James, can it be related to your recent landing? Yes, this is definitely me. The typeof check (http://mxr.mozilla.org/mozilla-central/source/b2g/components/test/unit/test_logcapture_gonk.js#37) should be taken out. I should have realized that it would be slow enough to timeout.

Flags: needinfo?(hobinjk)

Comment hidden (Legacy TBPL/Treeherder Robot)

jhobin

Comment 55

•

9 years ago

(In reply to James Hobin [:hobinjk] from comment #53) > (In reply to Alexandre LISSY :gerard-majax from comment #52) > > James, can it be related to your recent landing? > > Yes, this is definitely me. The typeof check > (http://mxr.mozilla.org/mozilla-central/source/b2g/components/test/unit/ > test_logcapture_gonk.js#37) should be taken out. I should have realized that > it would be slow enough to timeout. I misread the filename. test_logshake_gonk is a pure interaction with the LogShake object and shouldn't be having issues based on anything I have recently changed. I will be investigating this today.

James Hobin [:hobinjk]

Comment 56

•

9 years ago

Attached patch bug1144499.patch — Details — Splinter Review

I misread the filename. test_logshake_gonk is a pure interaction with the LogShake object and shouldn't be having issues based on anything I have recently changed. Upon investigating this further it looks like the File IO that LogShake uses is just really slow. I removed some unnecessary duplication in the test and pushed to try with this patch, which should fix the intermittent by making the test much faster. Try build: https://treeherder.mozilla.org/#/jobs?repo=try&revision=fe85b6458a70

Attachment #8624861 - Flags: review?(lissyx+mozillians)

Comment hidden (Legacy TBPL/Treeherder Robot)

:gerard-majax

Assignee

Updated

•

9 years ago

Attachment #8624861 - Flags: review?(lissyx+mozillians) → review+

:gerard-majax

Assignee

Comment 58

•

9 years ago

wooa: > 21:56:52 INFO - TEST-PASS | b2g/components/test/unit/test_logshake_gonk.js | took 146704ms on your try :)

:gerard-majax

Assignee

Comment 59

•

9 years ago

I triggered some retry to make sure.

:gerard-majax

Assignee

Comment 60

•

9 years ago

(In reply to Alexandre LISSY :gerard-majax from comment #59) > I triggered some retry to make sure. Much retriggers, much X1 green. The few oranges are OCSP tests.

Comment hidden (Legacy TBPL/Treeherder Robot)

jhobin

Updated

•

9 years ago

Assignee: nobody → hobinjk

Keywords: checkin-needed

Comment hidden (Legacy TBPL/Treeherder Robot)

Pulsebot

Comment 70

•

9 years ago

https://hg.mozilla.org/integration/b2g-inbound/rev/c32116f21ebc

Keywords: checkin-needed

Ryan VanderMeulen [:RyanVM]

Comment 71

•

9 years ago

https://hg.mozilla.org/mozilla-central/rev/c32116f21ebc

Status: NEW → RESOLVED

Closed: 9 years ago

status-firefox41: --- → fixed

Flags: in-testsuite+

Resolution: --- → FIXED

Target Milestone: --- → FxOS-S2 (10Jul)

Ryan VanderMeulen [:RyanVM]

Updated

•

9 years ago

status-b2g-v2.2: --- → affected

status-b2g-v2.5: --- → fixed

status-b2g-master: --- → fixed

status-firefox39: --- → wontfix

status-firefox40: --- → wontfix

status-firefox-esr31: --- → unaffected

status-firefox-esr38: --- → unaffected

Ryan VanderMeulen [:RyanVM]

Comment 72

•

9 years ago

https://hg.mozilla.org/releases/mozilla-b2g37_v2_2/rev/76db22807175

status-b2g-v2.2: affected → fixed

Norry.L.F(Leave from Mozilla)

Updated

•

9 years ago

status-b2g-v2.5: fixed → ---

Comment hidden (Legacy TBPL/Treeherder Robot)

James Hobin [:hobinjk]

Comment 75

•

9 years ago

Could this be the Settings queue head being blocked for 200+ seconds? I don't see why the test itself would be an issue (although maybe it needs to allow the GC to reclaim the settings lock?)

Flags: needinfo?(lissyx+mozillians)

:gerard-majax

Assignee

Comment 76

•

9 years ago

Logs shows that: - we do have a settings in flight since already 500 secs when we start the core logshake testing - this part of the testing is intensive

Flags: needinfo?(lissyx+mozillians)

Comment hidden (Legacy TBPL/Treeherder Robot)

Phil Ringnalda (:philor)

Updated

•

9 years ago

Status: RESOLVED → REOPENED

Resolution: FIXED → ---

Comment hidden (Legacy TBPL/Treeherder Robot)

log: https://treeherder.mozilla.org/logviewer.html#?repo=mozilla-inbound&job_id=14111069 repository: mozilla-inbound start_time: 2015-09-14T21:32:53 who: nigelbabu[at]gmail[dot]com machine: bld-linux64-spot-430 buildname: Linux x86-64 mozilla-inbound spidermonkey_info-warnaserr build revision: 67d8993c8511 CalledProcessError: Command '['hg', 'log', '-r', '67d8993c85116854ca1f291b9363f44d6fb73ff5', '--template', '{node}']' returned non-zero exit status 255 IOError: [Errno 2] No such file or directory: '/usr/local/lib/hgext/bundleclone.py' /builds/slave/m-in_l64_sm-we-000000000000000/src/config/pathsub.c:107:2: error: passing argument 1 of 'fail' discards 'const' qualifier from pointer target type [-Werror] /builds/slave/m-in_l64_sm-we-000000000000000/src/config/pathsub.c:110:6: error: passing argument 1 of 'fail' discards 'const' qualifier from pointer target type [-Werror] /builds/slave/m-in_l64_sm-we-000000000000000/src/config/pathsub.c:124:2: error: passing argument 1 of 'fail' discards 'const' qualifier from pointer target type [-Werror] /builds/slave/m-in_l64_sm-we-000000000000000/src/config/pathsub.c:149:2: error: passing argument 1 of 'fail' discards 'const' qualifier from pointer target type [-Werror] /builds/slave/m-in_l64_sm-we-000000000000000/src/config/pathsub.c:200:3: error: passing argument 1 of 'fail' discards 'const' qualifier from pointer target type [-Werror] /builds/slave/m-in_l64_sm-we-000000000000000/src/config/pathsub.c:207:6: error: passing argument 1 of 'xchdir' discards 'const' qualifier from pointer target type [-Werror] make[3]: *** [host_pathsub.o] Error 1 make[3]: *** Waiting for unfinished jobs.... /builds/slave/m-in_l64_sm-we-000000000000000/src/config/nsinstall.c:111:2: error: passing argument 1 of 'fail' discards 'const' qualifier from pointer target type [-Werror] /builds/slave/m-in_l64_sm-we-000000000000000/src/config/nsinstall.c:127:2: error: passing argument 1 of 'fail' discards 'const' qualifier from pointer target type [-Werror] /builds/slave/m-in_l64_sm-we-000000000000000/src/config/nsinstall.c:144:5: error: passing argument 1 of 'fail' discards 'const' qualifier from pointer target type [-Werror] /builds/slave/m-in_l64_sm-we-000000000000000/src/config/nsinstall.c:157:7: error: passing argument 1 of 'fail' discards 'const' qualifier from pointer target type [-Werror] /builds/slave/m-in_l64_sm-we-000000000000000/src/config/nsinstall.c:170:7: error: passing argument 1 of 'fail' discards 'const' qualifier from pointer target type [-Werror] /builds/slave/m-in_l64_sm-we-000000000000000/src/config/nsinstall.c:173:5: error: passing argument 1 of 'fail' discards 'const' qualifier from pointer target type [-Werror] /builds/slave/m-in_l64_sm-we-000000000000000/src/config/nsinstall.c:176:5: error: passing argument 1 of 'fail' discards 'const' qualifier from pointer target type [-Werror] /builds/slave/m-in_l64_sm-we-000000000000000/src/config/nsinstall.c:183:7: error: passing argument 1 of 'fail' discards 'const' qualifier from pointer target type [-Werror] /builds/slave/m-in_l64_sm-we-000000000000000/src/config/nsinstall.c:190:5: error: passing argument 1 of 'fail' discards 'const' qualifier from pointer target type [-Werror] /builds/slave/m-in_l64_sm-we-000000000000000/src/config/nsinstall.c:193:5: error: passing argument 1 of 'fail' discards 'const' qualifier from pointer target type [-Werror] /builds/slave/m-in_l64_sm-we-000000000000000/src/config/nsinstall.c:197:5: error: passing argument 1 of 'fail' discards 'const' qualifier from pointer target type [-Werror] /builds/slave/m-in_l64_sm-we-000000000000000/src/config/nsinstall.c:228:5: error: passing argument 1 of 'fail' discards 'const' qualifier from pointer target type [-Werror] /builds/slave/m-in_l64_sm-we-000000000000000/src/config/nsinstall.c:234:5: error: passing argument 1 of 'fail' discards 'const' qualifier from pointer target type [-Werror] /builds/slave/m-in_l64_sm-we-000000000000000/src/config/nsinstall.c:323:2: error: passing argument 1 of 'fail' discards 'const' qualifier from pointer target type [-Werror] /builds/slave/m-in_l64_sm-we-000000000000000/src/config/nsinstall.c:377:3: error: passing argument 1 of 'fail' discards 'const' qualifier from pointer target type [-Werror] /builds/slave/m-in_l64_sm-we-000000000000000/src/config/nsinstall.c:379:3: error: passing argument 1 of 'fail' discards 'const' qualifier from pointer target type [-Werror] /builds/slave/m-in_l64_sm-we-000000000000000/src/config/nsinstall.c:382:17: error: passing argument 1 of 'fail' discards 'const' qualifier from pointer target type [-Werror] /builds/slave/m-in_l64_sm-we-000000000000000/src/config/nsinstall.c:423:3: error: passing argument 1 of 'fail' discards 'const' qualifier from pointer target type [-Werror] make[3]: *** [host_nsinstall.o] Error 1 make[2]: *** [config/host] Error 2 make[1]: *** [export] Error 2 make: *** [default] Error 2

Comment hidden (Legacy TBPL/Treeherder Robot)

:gerard-majax

Assignee

Comment 148

•

9 years ago

Frequency seems to have highly increased on the past days, can we check what changed?

Comment hidden (Legacy TBPL/Treeherder Robot)

log: https://treeherder.mozilla.org/logviewer.html#?repo=try&job_id=11459654 repository: try start_time: 2015-09-15T07:59:59 who: hbambas[at]mozilla[dot]com machine: tst-linux32-spot-1021 buildname: Ubuntu VM 12.04 try debug test mochitest-jetpack revision: e3fd8dbb50c5 TEST-UNEXPECTED-FAIL | jetpack-package/addon-sdk/source/test/test-tabs.js.testAutomaticDestroyEventClose | Test timed out (after: START) TEST-UNEXPECTED-FAIL | jetpack-package/addon-sdk/source/test/test-ui-sidebar.js.testDetachEventOnWindowClose | Test timed out (after: no sidebar is showing) TEST-UNEXPECTED-FAIL | jetpack-package/addon-sdk/source/test/test-ui-sidebar.js.testDetachEventOnWindowClose | Should not be any unexpected windows open TEST-UNEXPECTED-FAIL | jetpack-package/addon-sdk/source/test/test-ui-sidebar.js.testSideBarIsShowingInNewWindows | Test timed out (after: show event fired) TEST-UNEXPECTED-FAIL | jetpack-package/addon-sdk/source/test/test-ui-sidebar.js.testSideBarIsShowingInNewWindows | Should not be any unexpected windows open TEST-UNEXPECTED-FAIL | jetpack-package/addon-sdk/source/test/test-ui-sidebar.js.testSidebarBasicLifeCycle | no sidebar is showing - true == false TEST-UNEXPECTED-FAIL | jetpack-package/addon-sdk/source/test/test-ui-sidebar.js.testSidebarBasicLifeCycle | there are no extra sidebar menuitems - false == true TEST-UNEXPECTED-FAIL | jetpack-package/addon-sdk/source/test/test-ui-sidebar.js.testSidebarBasicLifeCycle | sidebar is not showing 1 - true == false TEST-UNEXPECTED-FAIL | jetpack-package/addon-sdk/source/test/test-ui-sidebar.js.testSidebarBasicLifeCycle | there is one extra sidebar menuitems - 2 == 1 TEST-UNEXPECTED-FAIL | jetpack-package/addon-sdk/source/test/test-ui-sidebar.js.testSidebarBasicLifeCycle | the only extra menuitem is the one for our sidebar. - { // [object XULElement] TEST-UNEXPECTED-FAIL | jetpack-package/addon-sdk/source/test/test-ui-sidebar.js.testSidebarBasicLifeCycle | sidebar is not showing 2 - true == false TEST-UNEXPECTED-FAIL | jetpack-package/addon-sdk/source/test/test-ui-sidebar.js.testSidebarBasicLifeCycle | Test timed out (after: showing sidebar..) TEST-UNEXPECTED-FAIL | jetpack-package/addon-sdk/source/test/test-ui-sidebar.js.testSidebarGettersAndSettersAfterDestroy | no sidebar is showing - true == false TEST-UNEXPECTED-FAIL | jetpack-package/addon-sdk/source/test/test-ui-sidebar.js.testSidebarGettersAndSettersAfterDestroy | no sidebar is showing - true == false TEST-UNEXPECTED-FAIL | jetpack-package/addon-sdk/source/test/test-ui-sidebar.js.testSidebarLeakCheckDestroyAfterAttach | no sidebar is showing - true == false TEST-UNEXPECTED-FAIL | jetpack-package/addon-sdk/source/test/test-ui-sidebar.js.testSidebarLeakCheckDestroyAfterAttach | Test timed out (after: showing the sidebar) TEST-UNEXPECTED-FAIL | jetpack-package/addon-sdk/source/test/test-ui-sidebar.js.testSidebarLeakCheckUnloadAfterAttach | no sidebar is showing - true == false TEST-UNEXPECTED-FAIL | jetpack-package/addon-sdk/source/test/test-ui-sidebar.js.testSidebarLeakCheckUnloadAfterAttach | no sidebar is showing - true == false TEST-UNEXPECTED-FAIL | jetpack-package/addon-sdk/source/test/test-ui-sidebar.js.testSidebarUnload | no sidebar is showing - true == false TEST-UNEXPECTED-FAIL | jetpack-package/addon-sdk/source/test/test-ui-sidebar.js.testSidebarUnload | Test timed out (after: the current window is not private) TEST-UNEXPECTED-FAIL | jetpack-package/addon-sdk/source/test/test-ui-sidebar.js.testTitleSetter | no sidebar is showing - true == false TEST-UNEXPECTED-FAIL | jetpack-package/addon-sdk/source/test/test-ui-sidebar.js.testTitleSetter | Test timed out (after: title getter works) TEST-UNEXPECTED-FAIL | jetpack-package/addon-sdk/source/test/test-ui-sidebar.js.testTwoSidebarsWithSameTitleAndURL | no sidebar is showing - true == false TEST-UNEXPECTED-FAIL | jetpack-package/addon-sdk/source/test/test-ui-sidebar.js.testTwoSidebarsWithSameTitleAndURL | no sidebar is showing - true == false TEST-UNEXPECTED-FAIL | jetpack-package/addon-sdk/source/test/test-ui-sidebar.js.testURLSetter | no sidebar is showing - true == false TEST-UNEXPECTED-FAIL | jetpack-package/addon-sdk/source/test/test-ui-sidebar.js.testURLSetter | the new window sidebar is not showing - true == false TEST-UNEXPECTED-FAIL | jetpack-package/addon-sdk/source/test/test-ui-sidebar.js.testURLSetter | no sidebar is showing - true == false TEST-UNEXPECTED-FAIL | jetpack-package/addon-sdk/source/test/test-ui-sidebar.js.testURLSetterToSameValueReloadsSidebar | no sidebar is showing - true == false TEST-UNEXPECTED-FAIL | jetpack-package/addon-sdk/source/test/test-ui-sidebar.js.testURLSetterToSameValueReloadsSidebar | the new window sidebar is not showing - true == false TEST-UNEXPECTED-FAIL | jetpack-package/addon-sdk/source/test/test-ui-sidebar.js.testURLSetterToSameValueReloadsSidebar | no sidebar is showing - true == false TEST-UNEXPECTED-FAIL | jetpack-package/addon-sdk/source/test/test-ui-sidebar.js.testUndefinedID | no sidebar is showing - true == false TEST-UNEXPECTED-FAIL | jetpack-package/addon-sdk/source/test/test-ui-sidebar.js.testUndefinedID | no sidebar is showing - true == false TEST-UNEXPECTED-FAIL | jetpack-package/addon-sdk/source/test/test-ui-toolbar.js.test toolbar unload | Test timed out (after: START) TEST-UNEXPECTED-FAIL | jetpack-package/addon-sdk/source/test/test-ui-toolbar.js.test toolbar unload | Should not be any unexpected windows open TEST-UNEXPECTED-FAIL | jetpack-package/addon-sdk/source/test/test-ui-toolbar.js.test toolbar unload | detached from both windows on unload - false == true

Comment hidden (Legacy TBPL/Treeherder Robot)

James Hobin [:hobinjk]

Comment 326

•

9 years ago

Last time this was fixed by increasing the performance of individual tests. The fact that this has begun happening again points to a performance or memory regression. This can likely be fixed by removing the memory capturing in all of the existing tests and moving it to a new one. It may be worthwhile to just look at why the emulators are so terrible.

Comment hidden (Legacy TBPL/Treeherder Robot)

:gerard-majax

Assignee

Comment 431

•

9 years ago

It's definitively something making all the code or I would bet IOs slower: infra ? bug ? When I compare a recent mozilla-central green X1: > 17:32:06 INFO - TEST-PASS | b2g/components/test/unit/test_logcapture.js | took 20118ms > 17:33:59 INFO - TEST-PASS | b2g/components/test/unit/test_logcapture_gonk.js | took 110944ms > 17:34:28 INFO - TEST-PASS | b2g/components/test/unit/test_logparser.js | took 26014ms > 17:35:43 INFO - TEST-PASS | b2g/components/test/unit/test_logshake.js | took 73127ms With a recent failure: > 20:45:18 INFO - TEST-PASS | b2g/components/test/unit/test_logcapture.js | took 23188ms > 20:47:34 INFO - TEST-PASS | b2g/components/test/unit/test_logcapture_gonk.js | took 133320ms > 20:48:06 INFO - TEST-PASS | b2g/components/test/unit/test_logparser.js | took 30162ms > 20:49:44 INFO - TEST-PASS | b2g/components/test/unit/test_logshake.js | took 94906ms Other tests are slower as well. A successfull run is already quite close to the limit: > 17:40:15 INFO - TEST-PASS | b2g/components/test/unit/test_logshake_gonk.js | took 269548ms If we take as a reference test_logcapture_gonk.js, we have a 20% increase (110s to 133s). If we consider the same increase on test_logshake_gonk, then we can expect the test to run in 320s instead of 270s. Given the timeout is at 300s, we get killed. That being said, I cannot tell if it's myself or what but on recent nightlies on my dogfood device, I do feel there is a certain latency in each app opening. Nicolas, I know some code recently landed on the js engine side that are adding memory reporting. Is that enabled ? Could it explains the increased processing time I am observing on those tests ?

Flags: needinfo?(nicolas.b.pierron)

Comment hidden (Legacy TBPL/Treeherder Robot)

Selena Deckelmann :selenamarie :selena

Updated

•

9 years ago

Whiteboard: [b2g-build-support]

Nicolas B. Pierron [:nbp]

Comment 449

•

9 years ago

(In reply to Alexandre LISSY :gerard-majax from comment #431) > Nicolas, I know some code recently landed on the js engine side that are > adding memory reporting. Is that enabled ? Could it explains the increased > processing time I am observing on those tests ? I don't think any memory reporting is enabled by default without having it be enabled explicitly. Still, I will forward the question to Jim. (see comment 431)

Flags: needinfo?(nicolas.b.pierron) → needinfo?(jimb)

Comment hidden (Legacy TBPL/Treeherder Robot)

Comment hidden (Intermittent Failures Robot)

Phil Ringnalda (:philor)

Comment 533

•

9 years ago

https://treeherder.mozilla.org/#/jobs?repo=b2g-inbound&fromchange=cb44ba24be12&filter-tier=1&filter-searchStr=5025eb0fdc7470892a30d3397f75ce446e48e091&tochange=2d4f2af678ee Fixed by bug 1204837

Assignee: hobinjk → nobody

Status: REOPENED → RESOLVED

Closed: 9 years ago → 9 years ago

Depends on: 1204837

Flags: needinfo?(jimb)

Resolution: --- → FIXED

Comment hidden (Intermittent Failures Robot)

Phil Ringnalda (:philor)

Comment 535

•

9 years ago

Wow, you regress your perf quite a lot, don't you?

Status: RESOLVED → REOPENED

Resolution: FIXED → ---

:gerard-majax

Assignee

Comment 536

•

9 years ago

(In reply to Phil Ringnalda (:philor) from comment #535) > Wow, you regress your perf quite a lot, don't you? Do you mind giving more informations ? Previous regression was a legit issue on Gecko. Nothing has changed on that test or code recently. If it is timeout again, then we should start finding the reason why.

Flags: needinfo?(philringnalda)

:gerard-majax

Assignee

Comment 537

•

9 years ago

So for once I have been able to make use of Orange Factor. I have re-triggered a lot of the B2G ICS Emulator Debug X1 instances to try to identify the time when intermittence starts. Hopefully that will guide us toward that new perf regression.

Flags: needinfo?(philringnalda)

Phil Ringnalda (:philor)

Comment 538

•

9 years ago

My mistake, I had already backed out the regressor.

Status: REOPENED → RESOLVED

Closed: 9 years ago → 9 years ago

Resolution: --- → FIXED

:gerard-majax

Assignee

Comment 539

•

9 years ago

(In reply to Phil Ringnalda (:philor) from comment #538) > My mistake, I had already backed out the regressor. Awesome, thanks! Which bug was it, just out of curiosity?

Comment hidden (Intermittent Failures Robot)

:gerard-majax

Assignee

Comment 543

•

9 years ago

(In reply to OrangeFactor Robot from comment #542) > 5 automation job failures were associated with this bug in the last 7 days. > > Repository breakdown: > * b2g-inbound: 2 > * mozilla-inbound: 1 > * mozilla-central: 1 > * fx-team: 1 > > Platform breakdown: > * b2g-emu-ics: 5 > > For more details, see: > https://brasstacks.mozilla.com/orangefactor/ > ?display=Bug&bugid=1144499&startday=2015-10-26&endday=2015-11-01&tree=all Looks like we have a perf regression that is arriving, given bug 1220634.

Comment hidden (Intermittent Failures Robot)

Ben Kelly [:bkelly, not reviewing]

Updated

•

9 years ago

Status: RESOLVED → REOPENED

Resolution: FIXED → ---

Kyle Lahnakoski [:ekyle]

Comment 551

•

9 years ago

Attached image Test times for test_logshake_gonk.js — Details

It appears the test times are hitting a 300sec limit.

:gerard-majax

Assignee

Comment 552

•

9 years ago

(In reply to Kyle Lahnakoski [:ekyle] from comment #551) > Created attachment 8701478 [details] > Test times for test_logshake_gonk.js > > It appears the test times are hitting a 300sec limit. Which, as you can see in the history of this bug, as always been correlated to landing of gecko-side perf regressions. Sadly, treeherder is totally unusable for me when I try to search over long period of time to find with which patch this started. I warned about that two months ago in comment 543.

Comment hidden (Intermittent Failures Robot)

:gerard-majax

Assignee

Comment 561

•

9 years ago

Attached patch Allow test_logshake_gonk.js to be longer — Details — Splinter Review

Attachment #8705700 - Flags: review+

:gerard-majax

Assignee

Comment 562

•

9 years ago

green enough: https://treeherder.mozilla.org/#/jobs?repo=try&revision=2eea59ff440f

Flags: needinfo?(mhenretty)

Flags: needinfo?(bkelly)

Keywords: checkin-needed

:gerard-majax

Assignee

Updated

•

9 years ago

Assignee: nobody → lissyx+mozillians

Comment hidden (Intermittent Failures Robot)

Pulsebot

Comment 564

•

9 years ago

https://hg.mozilla.org/integration/b2g-inbound/rev/2c2e20d052e8

Keywords: checkin-needed

Phil Ringnalda (:philor)

Comment 565

•

9 years ago

bugherder

https://hg.mozilla.org/mozilla-central/rev/2c2e20d052e8

Status: REOPENED → RESOLVED

Closed: 9 years ago → 9 years ago

status-firefox46: --- → fixed

Resolution: --- → FIXED

Comment hidden (Intermittent Failures Robot)

Michael Henretty [:mikehenrty][:mhenretty]

Comment 567

•

9 years ago

Definitely an improvement.

Flags: needinfo?(mhenretty)

Ben Kelly [:bkelly, not reviewing]

Updated

•

9 years ago

Flags: needinfo?(bkelly)

bug1144499.patch 9 years ago James Hobin [:hobinjk] 1.85 KB, patch	gerard-majax : review+	Details \| Diff \| Splinter Review
Test times for test_logshake_gonk.js 9 years ago Kyle Lahnakoski [:ekyle] 198.94 KB, image/png		Details
Allow test_logshake_gonk.js to be longer 9 years ago :gerard-majax 999 bytes, patch	gerard-majax : review+	Details \| Diff \| Splinter Review