New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 619765 link

Starred by 1 user

Issue metadata

Status: Untriaged
Owner: ----
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 1
Type: Bug



Sign in to add a comment

GN: content_browsertests failure in OutOfProcessPPAPITest with use_ozone=true

Project Member Reported by steve...@chromium.org, Jun 14 2016

Issue description

The test appears to be failing to load the default font.

Example failure:

utOfProcessPPAPITest.BrowserFont (run #1):
[ RUN      ] OutOfProcessPPAPITest.BrowserFont
[12156:12156:0610/223418:20428550956:WARNING:audio_manager.cc(297)] Multiple instances of AudioManager detected
[12156:12156:0610/223418:20428550990:WARNING:audio_manager.cc(271)] Multiple instances of AudioManager detected
[12156:12156:0610/223418:20428565200:ERROR:proxy_service.cc(1541)] ProxyConfigService for ChromeOS should be created in profile_io_data.cc::CreateProxyConfigService and this should be used only for examples.
[12156:12156:0610/223418:20428681782:INFO:CONSOLE(177)] "FontFamilies finished in 0.003 seconds.", source: file:///tmp/isolated_runZAQdoJ/ppapi/tests/test_case.html?testcase=BrowserFont (177)
[12156:12156:0610/223418:20428696625:INFO:CONSOLE(177)] "Measure finished in 0.003 seconds.", source: file:///tmp/isolated_runZAQdoJ/ppapi/tests/test_case.html?testcase=BrowserFont (177)
[12156:12156:0610/223418:20428697591:INFO:CONSOLE(177)] "MeasureRTL finished in 0.001 seconds.", source: file:///tmp/isolated_runZAQdoJ/ppapi/tests/test_case.html?testcase=BrowserFont (177)
[12156:12156:0610/223418:20428699002:INFO:CONSOLE(177)] "CharPos finished in 0.001 seconds.", source: file:///tmp/isolated_runZAQdoJ/ppapi/tests/test_case.html?testcase=BrowserFont (177)
[12156:12156:0610/223418:20428700187:INFO:CONSOLE(177)] "Draw finished in 0.012 seconds.", source: file:///tmp/isolated_runZAQdoJ/ppapi/tests/test_case.html?testcase=BrowserFont (177)
../../content/test/ppapi/ppapi_test.cc:101: Failure
Value of: handler.message().c_str()
  Actual: "FontFamilies FAIL: Failure in ../../ppapi/tests/test_browser_font.cc(42): !families.AsString().empty()"
Expected: "PASS"
[  FAILED  ] OutOfProcessPPAPITest.BrowserFont, where TypeParam =  and GetParam() =  (204 ms)



 
I did some poking around and it is entirely unclear to me why this would be failing just for ozone.

I checked and the tests do run and pass with GYP with GYP_DEFINES="use_goma=1 chromeos=1 use_ozone=1"

Example failure:
https://build.chromium.org/p/tryserver.chromium.linux/builders/linux_chromium_chromeos_ozone_rel_ng/builds/184706/steps/content_browsertests%20%28with%20patch%29%20on%20Ubuntu-12.04

Project Member

Comment 2 by bugdroid1@chromium.org, Jun 16 2016

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

commit 98afc7a88ebf27d0b5e765ab112fbc6778cd3f05
Author: dpranke <dpranke@chromium.org>
Date: Thu Jun 16 19:49:25 2016

Disable remaining tests that fail on the Linux desktop CrOS GN builds.

This CL disables five tests that currently fail on the builders, so that
we can flip the builders from GYP to GN without waiting for them to be
fixed.

R=stevenjb@chromium.org, brettw@chromium.org, dcastagna@chromium.org
BUG= 618516 , 619765,  619784 

Review-Url: https://codereview.chromium.org/2071703002
Cr-Commit-Position: refs/heads/master@{#400235}

[modify] https://crrev.com/98afc7a88ebf27d0b5e765ab112fbc6778cd3f05/chrome/browser/extensions/extension_commands_global_registry_apitest.cc
[modify] https://crrev.com/98afc7a88ebf27d0b5e765ab112fbc6778cd3f05/content/test/ppapi/ppapi_browsertest.cc
[modify] https://crrev.com/98afc7a88ebf27d0b5e765ab112fbc6778cd3f05/ui/gl/gl_image_ozone_native_pixmap_drm_unittest.cc

Labels: -Proj-GN-Migration
Owner: ----
Status: Untriaged (was: Assigned)
I don't think this needs to block the GYP->GN migration
Components: Internals>Plugins>Pepper
Project Member

Comment 5 by bugdroid1@chromium.org, May 3 2017

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

commit e3cfa1285898021bfe5bd4e62ddd94d0e97e6e93
Author: kylechar <kylechar@chromium.org>
Date: Wed May 03 14:26:14 2017

Disable *.TrueTypeFont browser_test for Ozone CrOS.

These tests are already disabled in content_browsertests for Ozone CrOS.
They aren't disabled in browser_tests, probably because it's not run as
part of CQ.

The implementation of TrueType font information is missing for Ozone
because pango isn't compiled. This is probably the reason why the tests
fail.

BUG=619765

Review-Url: https://codereview.chromium.org/2856963002
Cr-Commit-Position: refs/heads/master@{#468961}

[modify] https://crrev.com/e3cfa1285898021bfe5bd4e62ddd94d0e97e6e93/chrome/test/ppapi/ppapi_browsertest.cc

Sign in to add a comment