benchmarks.system_health_smoke_test.SystemHealthBenchmarkSmokeTest.system_health.memory_desktop.browse:search:google failing on Mac10.11 |
|||||||
Issue descriptionConsistently. e.g. https://build.chromium.org/p/chromium.mac/builders/Mac10.11%20Tests/builds/16630 Browser stdout (abbreviated): DevTools listening on ws://127.0.0.1:58340/devtools/browser/032358f8-b695-440a-8eca-286d2a59472b Received signal 11 SEGV_MAPERR 000000000000 [0x00011010591c] [0x000110105811] [0x7fff8722052a] [0x7fff78355ec0] [0x7fff8cd09718] [0x7fff8cd0968a] [0x7fff8cd0941c] [0x7fff8cd092ed] [0x7fff8cd08b3d] [0x7fff8622bb19] [0x7fff8622b5c5] [0x7fff86230472] [0x7fff8623147f] Browser log: [10931:1295:0816/051853.630008:INFO:CONSOLE(0)] "Access to Font at 'https://fonts.gstatic.com/s/roboto/v15/oMMgfZMQthOryQo9n22dcuvvDin1pK8aKteLpeZ5c0A.woff2' from origin 'https://www.google.com' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource. Origin 'https://www.google.com' is therefore not allowed access. The response had HTTP status code 404.", source: https://www.google.com/search?q=flower (0) [10931:1295:0816/051853.630149:INFO:CONSOLE(0)] "Access to Font at 'https://fonts.gstatic.com/s/roboto/v15/d-6IYplOFocCacKzxwXSOJBw1xU1rKptJj_0jans920.woff2' from origin 'https://www.google.com' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource. Origin 'https://www.google.com' is therefore not allowed access. The response had HTTP status code 404.", source: https://www.google.com/search?q=flower (0) [10931:1295:0816/051853.630762:INFO:CONSOLE(0)] "Uncaught (in promise) NetworkError: A network error occurred.", source: https://www.google.com/search?q=flower (0) [10931:1295:0816/051853.630860:INFO:CONSOLE(0)] "Uncaught (in promise) NetworkError: A network error occurred.", source: https://www.google.com/search?q=flower (0) [10931:1295:0816/051853.630943:INFO:CONSOLE(0)] "Uncaught (in promise) NetworkError: A network error occurred.", source: https://www.google.com/search?q=flower (0) [10931:1295:0816/051853.631046:INFO:CONSOLE(0)] "Uncaught (in promise) NetworkError: A network error occurred.", source: https://www.google.com/search?q=flower (0)
,
Aug 16 2017
Helen: any idea about this network error? I wonder whether it related to the timing
,
Aug 16 2017
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/262c05e23b85a9a2cfd44a44250ea402080080b7 commit 262c05e23b85a9a2cfd44a44250ea402080080b7 Author: Jeremy Roman <jbroman@chromium.org> Date: Wed Aug 16 13:52:34 2017 Disable failing memory_desktop.browse:search:google smoke test (telemetry_perf_unittests). By the authority of Chromium sheriff. Bug: 755969 Change-Id: If27affaa5bd0904f3a4d0cc89179ef9964966cef No-Try: true Tbr: nednguyen@google.com Reviewed-on: https://chromium-review.googlesource.com/616708 Reviewed-by: Jeremy Roman <jbroman@chromium.org> Commit-Queue: Jeremy Roman <jbroman@chromium.org> Cr-Commit-Position: refs/heads/master@{#494762} [modify] https://crrev.com/262c05e23b85a9a2cfd44a44250ea402080080b7/tools/perf/benchmarks/system_health_smoke_test.py
,
Aug 16 2017
I haven't seen that the error before. The CORS error shouldn't be fatal. Is that a Chrome crash? Can we symbolize the stack trace?
,
Aug 16 2017
,
Aug 16 2017
No sure why there is no symbolized stack trace here, but this is likely a crash: Received signal 11 SEGV_MAPERR 000000000000 [0x000105c9391c] [0x000105c93811] [0x7fff8722052a] [0x7fff78355ec0] [0x7fff8cd09718] [0x7fff8cd0968a] [0x7fff8cd0941c] [0x7fff8cd092ed] [0x7fff8cd08b3d] [0x7fff8622bb19] [0x7fff8622b5c5] [0x7fff86230472] [0x7fff8623147f] [0x000108a42baf] [0x000108a369a4] [0x000108a35f82] [0x000108a3626a] [0x000108a4b039] [0x000108a4c2f8] [0x000108a4c955] [0x000108a46556] [0x000108a48126] [0x000108a481d5] [0x000108a47583] [0x000108a2a018] [0x0001092e9f4e] [0x0001092e8664] [0x000109212496] [0x000109211715] [0x000109215c0f] [0x0001091ff3f1] [0x0001091ff011] [0x0001091f6a64] [0x000109201981] [0x000109201d35] [0x000109200cef] [0x0001091ff3e0] [0x0001091ff011] [0x0001091f6a64] [0x000109201981] [0x000109201d35] [0x000109200cef] [0x0001091ff3e0] [0x0001091ff011] [0x0001091f6a64] [0x000109201981] [0x000109201d35] [0x000109200cef] [0x0001091ff3e0] [0x0001091ff011] [0x0001091f6a64] [0x000109201981] [0x000109201d35] [0x000109200cef] [0x0001091ff3e0] [0x0001091ff011] [0x0001091f6a64] [0x0001091f7dd3] [0x0001091f7ac1] [0x0001091ff1be] [0x0001091f6a64] [0x0001092c34c4] [end of stack trace]
,
Aug 16 2017
This is hard to resolve due to the lack of symbolized stack trace. So I mark this as blocked on issue 739881
,
Oct 17 2017
Logs from a more recent failure with a timeout: https://chromium-swarm.appspot.com/task?id=3943f6bbb8bd9410&refresh=10&show_raw=1
,
Oct 23 2017
Possibly related? Issue 773510
,
Oct 24 2017
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/5a49151320d67bf460014f01e12a40c709bccf3f commit 5a49151320d67bf460014f01e12a40c709bccf3f Author: Ned Nguyen <nednguyen@google.com> Date: Tue Oct 24 01:15:40 2017 Revert "Disable failing memory_desktop.browse:search:google smoke test (telemetry_perf_unittests)." This reverts commit 262c05e23b85a9a2cfd44a44250ea402080080b7. Reason for revert: try reenabling to see if this is still failing. Original change's description: > Disable failing memory_desktop.browse:search:google smoke test (telemetry_perf_unittests). > > By the authority of Chromium sheriff. > > Bug: 755969 > Change-Id: If27affaa5bd0904f3a4d0cc89179ef9964966cef > No-Try: true > Tbr: nednguyen@google.com > Reviewed-on: https://chromium-review.googlesource.com/616708 > Reviewed-by: Jeremy Roman <jbroman@chromium.org> > Commit-Queue: Jeremy Roman <jbroman@chromium.org> > Cr-Commit-Position: refs/heads/master@{#494762} TBR=jbroman@chromium.org,nednguyen@google.com # Not skipping CQ checks because original CL landed > 1 day ago. Bug: 755969 Change-Id: I853d0b816f1910a6ff7ca9489dd4df24adcd05d4 Reviewed-on: https://chromium-review.googlesource.com/734020 Commit-Queue: Ned Nguyen <nednguyen@google.com> Reviewed-by: Ned Nguyen <nednguyen@google.com> Cr-Commit-Position: refs/heads/master@{#510975} [modify] https://crrev.com/5a49151320d67bf460014f01e12a40c709bccf3f/tools/perf/benchmarks/system_health_smoke_test.py
,
Aug 2
,
Jan 16
,
Jan 16
|
|||||||
►
Sign in to add a comment |
|||||||
Comment 1 by jbroman@chromium.org
, Aug 16 2017Status: Assigned (was: Untriaged)