Issue metadata
Sign in to add a comment
|
"benchmarks.system_health_smoke_test.SystemHealthBenchmarkSmokeTest.system_health.memory_mobile.load:news:cnn" is flaky |
||||||||||||||||||||||||
Issue description"benchmarks.system_health_smoke_test.SystemHealthBenchmarkSmokeTest.system_health.memory_mobile.load:news:cnn" 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=ahVzfmNocm9taXVtLXRyeS1mbGFrZXNydwsSBUZsYWtlImxiZW5jaG1hcmtzLnN5c3RlbV9oZWFsdGhfc21va2VfdGVzdC5TeXN0ZW1IZWFsdGhCZW5jaG1hcmtTbW9rZVRlc3Quc3lzdGVtX2hlYWx0aC5tZW1vcnlfbW9iaWxlLmxvYWQ6bmV3czpjbm4M. 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
,
Jul 28 2017
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/615158f953597f05f17c7f207fe5154e29797649 commit 615158f953597f05f17c7f207fe5154e29797649 Author: Eddy Mead <meade@chromium.org> Date: Fri Jul 28 06:20:34 2017 [Chromium sheriff] Disable benchmark benchmarks.system_health_smoke_test.SystemHealthBenchmarkSmokeTest.system_health.memory_mobile.load:news:cnn It is flaky. See automatically filed bug http://crbug.com/749918 . TBR'ing a contributor to the test file. TBR=nednguyen@chromium.org Bug: 749918 Change-Id: I990173df9f40d89c32ec2d917b8b648043009e4f Reviewed-on: https://chromium-review.googlesource.com/590970 Reviewed-by: meade_UTC10 <meade@chromium.org> Commit-Queue: meade_UTC10 <meade@chromium.org> Cr-Commit-Position: refs/heads/master@{#490297} [modify] https://crrev.com/615158f953597f05f17c7f207fe5154e29797649/tools/perf/benchmarks/system_health_smoke_test.py
,
Jul 29 2017
Log: https://chromium-swarm.appspot.com/task?id=379f45d204aaae10&refresh=10&show_raw=1 signal 6 (SIGABRT), code -6 in tid 13270 (CrRendererMain) pid: 13257, tid: 13270, name: CrRendererMain >>> org.chromium.chrome:sandboxed_process0 <<< signal 6 (SIGABRT), code -6 (SI_TKILL), fault addr -------- [FATAL:ClassicPendingScript.cpp(172)] Check failed: GetResource()->IsLoaded(). Stack Trace: RELADDR FUNCTION FILE:LINE v------> std::__ndk1::__hash_const_iterator<std::__ndk1::__hash_node<std::__ndk1::__hash_value_type<int, cc::LayerImpl*>, void*>*> std::__ndk1::__hash_table<std::__ndk1::__hash_value_type<int, cc::LayerImpl*>, std::__ndk1::__unordered_map_hasher<int, std::__ndk1::__hash_value_type<int, cc::LayerImpl*>, std::__ndk1::hash<int>, true>, std::__ndk1::__unordered_map_equal<int, std::__ndk1::__hash_value_type<int, cc::LayerImpl*>, std::__ndk1::equal_to<int>, true>, std::__ndk1::allocator<std::__ndk1::__hash_value_type<int, cc::LayerImpl*> > >::find<int>(int const&) const /b/c/b/android_n5x_swarming_rel/src/third_party/android_tools/ndk/sources/cxx-stl/llvm-libc++/libcxx/include/__hash_table:2051 v------> std::__ndk1::unordered_map<int, cc::LayerImpl*, std::__ndk1::hash<int>, std::__ndk1::equal_to<int>, std::__ndk1::allocator<std::__ndk1::pair<int const, cc::LayerImpl*> > >::find(int const&) const /b/c/b/android_n5x_swarming_rel/src/third_party/android_tools/ndk/sources/cxx-stl/llvm-libc++/libcxx/include/unordered_map:972 00000000012fd89f cc::LayerTreeImpl::LayerById(int) const ... Since the check "FATAL:ClassicPendingScript.cpp(172)] Check failed: GetResource()->IsLoaded()." fail, assign this to vogelheim@ to triage further
,
Jul 31 2017
,
Aug 21 2017
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/8ebf13ab437d390d8ceeb7e36881fc690479f976 commit 8ebf13ab437d390d8ceeb7e36881fc690479f976 Author: Hiroshige Hayashizaki <hiroshige@chromium.org> Date: Mon Aug 21 17:45:24 2017 Re-enable tests disabled due to Issue 749773 Because https://chromium-review.googlesource.com/620272 fixes the crashing Issue 749773 , this CL re-enables the tests that were disabled due to the crash. Bug: 749773 , 749918 Change-Id: Icd69fe32fc58c112a87726cadd15647ab1109653 Reviewed-on: https://chromium-review.googlesource.com/623910 Reviewed-by: Ned Nguyen <nednguyen@google.com> Commit-Queue: Hiroshige Hayashizaki <hiroshige@chromium.org> Cr-Commit-Position: refs/heads/master@{#495980} [modify] https://crrev.com/8ebf13ab437d390d8ceeb7e36881fc690479f976/tools/perf/benchmarks/system_health_smoke_test.py
,
Jan 24 2018
|
|||||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||||
Comment 1 by meade@chromium.org
, Jul 28 2017Labels: -Sheriff-Chromium
Owner: nedngu...@google.com