"benchmarks.system_health_smoke_test.SystemHealthBenchmarkSmokeTest.system_health.memory_desktop.load:news:qq" is flaky |
|||||||||||
Issue description"benchmarks.system_health_smoke_test.SystemHealthBenchmarkSmokeTest.system_health.memory_desktop.load:news:qq" is flaky. This issue was created automatically by the chromium-try-flakes app. Please find the right owner to fix the respective test/step and assign this issue to them. If the step/test is infrastructure-related, please add Infra-Troopers label and change issue status to Untriaged. When done, please remove the issue from Sheriff Bug Queue by removing the Sheriff-Chromium label. We have detected 3 recent flakes. List of all flakes can be found at https://chromium-try-flakes.appspot.com/all_flake_occurrences?key=ahVzfmNocm9taXVtLXRyeS1mbGFrZXNydwsSBUZsYWtlImxiZW5jaG1hcmtzLnN5c3RlbV9oZWFsdGhfc21va2VfdGVzdC5TeXN0ZW1IZWFsdGhCZW5jaG1hcmtTbW9rZVRlc3Quc3lzdGVtX2hlYWx0aC5tZW1vcnlfZGVza3RvcC5sb2FkOm5ld3M6cXEM. Flaky tests should be disabled within 30 minutes unless culprit CL is found and reverted. Please see more details here: https://sites.google.com/a/chromium.org/dev/developers/tree-sheriffs/sheriffing-bug-queues#triaging-auto-filed-flakiness-bugs
,
Feb 28 2017
,
Feb 28 2017
I'm disabling this test.
,
Feb 28 2017
,
Feb 28 2017
nednguyen, skyostil: Can you assign someone for this?
,
Feb 28 2017
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/41ca6f1ea85eaf0105769ba88dd51e0b1aab6f3d commit 41ca6f1ea85eaf0105769ba88dd51e0b1aab6f3d Author: yutak <yutak@chromium.org> Date: Tue Feb 28 07:19:15 2017 Disable system_health.memory_desktop.load:news:qq. BUG=696824 TBR=fsamuel@chromium.org,sergeyu@chromium.org,dvadym@chromium.org Review-Url: https://codereview.chromium.org/2719323002 Cr-Commit-Position: refs/heads/master@{#453535} [modify] https://crrev.com/41ca6f1ea85eaf0105769ba88dd51e0b1aab6f3d/tools/perf/benchmarks/system_health_smoke_test.py
,
Feb 28 2017
Given the test was disabled, and an owner is assigned, I'm removing the sheriff label.
,
Feb 28 2017
Ken: based on the stack, it seems like this crash is related to GPU? Cc'ed memory-infra folks because this crashes upon a dump command.
,
Feb 28 2017
It looks like the GPU process can't start (presumably because it's running in a VM), the page contains some Flash content which was converted to HTML5 via Shumway, that content requires WebGL, and WebGL isn't available. The Shumway content then throws JavaScript exceptions and the page fails to load properly. I'd expect this to fail all the time if the benchmark runs on the same kind of VM all the time. I'll be at a conference today, so reassigning to vmiura@ for more follow-up today. Could the Speed team consider running all benchmarks on physical hardware with real GPUs? Or at least this one? Running in a VM is not representative of how real users run the browser.
,
Feb 28 2017
This is just a smoke test, the benchmark is also run elsewhere on real hardware. I think just disabling test as done in #6 should be fine.
,
Mar 23 2017
I'm not clear of this needs further action. Lowering the priority given that the test was disabled and per #10 doesn't seem high priority. What is the VM configuration and about:gpu information?
,
Mar 23 2017
GPU info:
OS: win win7
GPU device 0: VENDOR = 0x15ad, DEVICE = 0x405
GPU Attributes:
amd_switchable : False
basic_info_state : 1
context_info_state : 0
direct_rendering : True
driver_date : 7-28-2011
driver_vendor : VMware, Inc.
driver_version : 7.14.1.1070
dx_diagnostics_info_state: 0
gl_extensions :
gl_renderer :
gl_reset_notification_strategy: 0
gl_vendor :
gl_version :
gl_ws_extensions :
gl_ws_vendor :
gl_ws_version :
in_process_gpu : True
initialization_time : 0
jpeg_decode_accelerator_supported: False
max_msaa_samples :
optimus : False
passthrough_cmd_decoder: False
pixel_shader_version:
process_crash_count : 0
sandboxed : False
software_rendering : False
vertex_shader_version:
video_decode_accelerator_flags: 0
Feature Status:
2d_canvas : unavailable_software
flash_3d : unavailable_software
flash_stage3d : unavailable_software
flash_stage3d_baseline: unavailable_software
gpu_compositing : unavailable_software
multiple_raster_threads: unavailable_off
native_gpu_memory_buffers: disabled_software
rasterization : unavailable_software
video_decode : unavailable_software
video_encode : unavailable_software
vpx_decode : unavailable_software
webgl : unavailable_off
webgl2 : unavailable_off
Driver Bug Workarounds:
clear_uniforms_before_first_program_use
decode_encode_srgb_for_generatemipmap
disable_direct_composition
disable_discard_framebuffer
disable_dxgi_zero_copy_video
disable_framebuffer_cmaa
exit_on_context_lost
scalarize_vec_and_mat_constructor_args
(From https://chromium-swarm.appspot.com/task?id=349a5dfbbaef6810&refresh=10&show_raw=1)
,
Apr 6 2018
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue. Sorry for the inconvenience if the bug really should have been left as Available. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Aug 3
This bug has an owner, thus, it's been triaged. Changing status to "assigned".
,
Jan 16
,
Jan 16
|
|||||||||||
►
Sign in to add a comment |
|||||||||||
Comment 1 by yutak@chromium.org
, Feb 28 2017