New issue
Advanced search Search tips

Issue 830823 link

Starred by 1 user
Status: Fixed
Owner:
eseckler@chromium.org
Closed: Apr 2018
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 1
Type: Bug



Sign in to add a comment

"HeadlessRenderBrowserTestSvgExamples.RunAsyncTest" is flaky

Project Member Reported by chromium...@appspot.gserviceaccount.com, Apr 9 2018 
"HeadlessRenderBrowserTestSvgExamples.RunAsyncTest" 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=ahVzfmNocm9taXVtLXRyeS1mbGFrZXNyPAsSBUZsYWtlIjFIZWFkbGVzc1JlbmRlckJyb3dzZXJUZXN0U3ZnRXhhbXBsZXMuUnVuQXN5bmNUZXN0DA.

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

Comment 1 by vasi...@chromium.org, Apr 10 2018

Labels: -Sheriff-Chromium
Owner: eseckler@chromium.org
Status: Assigned (was: Untriaged)
[ RUN      ] HeadlessRenderBrowserTestSvgExamples.RunAsyncTest
[17219:17219:0410/054141.412661:5281519204:WARNING:resource_bundle.cc(347)] locale_file_path.empty() for locale 
[0410/054141.424924:WARNING:resource_bundle.cc(347)] locale_file_path.empty() for locale 
[17219:17219:0410/054141.429906:5281536448:ERROR:gpu_process_transport_factory.cc(1017)] Lost UI shared context.
[0410/054141.449779:WARNING:resource_bundle.cc(347)] locale_file_path.empty() for locale 
[17219:17219:0410/054141.692572:5281799118:ERROR:headless_render_test.cc(84)] Pixel (119,166): expected ffffcbcb actual ffffcccc
[17219:17219:0410/054141.696599:5281803141:ERROR:headless_render_test.cc(94)] Number of pixel with an error: 1
[17219:17219:0410/054141.696630:5281803171:ERROR:headless_render_test.cc(95)] Error Bounding Box : 119,166 1x1
[17219:17219:0410/054141.696642:5281803183:ERROR:headless_render_test.cc(96)] To update goldens, use --update-goldens.
../../headless/test/headless_render_test.cc:523: Failure
Value of: ScreenshotMatchesGolden(data, options.golden_file_name)
  Actual: false
Expected: true
[17219:17226:0410/054141.717673:5281824216:WARNING:discardable_shared_memory_manager.cc(436)] Some MojoDiscardableSharedMemoryManagerImpls are still alive. They will be leaked.
[17219:17264:0410/054141.719121:5281825664:WARNING:internal_linux.cc(64)] Failed to read /proc/17241/stat
[  FAILED  ] HeadlessRenderBrowserTestSvgExamples.RunAsyncTest, where TypeParam =  and GetParam() =  (345 ms)

Assigning to eseckler@chromium.org due to r549166

Comment 2 by eseckler@chromium.org, Apr 11 2018

Status: Started (was: Assigned)
Increasing error limit in crrev.com/c/1005006.
Project Member

Comment 3 by bugdroid1@chromium.org, Apr 11 2018 

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/38f2f7ba74def14b41dee935c2f17d86a7f34ee4

commit 38f2f7ba74def14b41dee935c2f17d86a7f34ee4
Author: Eric Seckler <eseckler@chromium.org>
Date: Wed Apr 11 09:05:08 2018

headless: Increase error limit for render test screenshots

Some tests are flaky, let's see if this helps.

Bug:  830823 
Change-Id: I48f0c8284ee8f94518bb4cc4c955fae3edddcdf4
TBR: alexclarke@chromium.org
Reviewed-on: https://chromium-review.googlesource.com/1005006
Reviewed-by: Eric Seckler <eseckler@chromium.org>
Commit-Queue: Eric Seckler <eseckler@chromium.org>
Cr-Commit-Position: refs/heads/master@{#549833}
[modify] https://crrev.com/38f2f7ba74def14b41dee935c2f17d86a7f34ee4/headless/test/headless_render_test.cc

Comment 4 by eseckler@chromium.org, Apr 11 2018

Status: Fixed (was: Started)
Looks like above patch resolved the flakiness - I didn't see any further flakes reported since then. Please reopen if the issue reappears.
►

Sign in to add a comment