Commits · b17047cc2007ca299baf2e3b2de12c2afdad6e5b · eriksson monteiro / tangled

28 Oct, 2014 13 commits

Use cpuused=6 for lossy VP9 mode · b17047cc

wez authored Oct 27, 2014

BUG=260879

Review URL: https://codereview.chromium.org/678073007

Cr-Commit-Position: refs/heads/master@{#301503}

b17047cc

Log SSL_READ_ERROR and SSL_WRITE_ERROR in SSLClientSocketOpenSSL. · b8c23215

davidben authored Oct 27, 2014

The equivalent logs in SSLClientSocketNSS were never implemented here. This
will help in debugging problems which occur after the handshake.

BUG=425834

Review URL: https://codereview.chromium.org/651183004

Cr-Commit-Position: refs/heads/master@{#301502}

b8c23215

Standardize usage of virtual/override/final specifiers. · 2dec45fb

dcheng authored Oct 27, 2014

The Google C++ style guide states:

  Explicitly annotate overrides of virtual functions or virtual
  destructors with an override or (less frequently) final specifier.
  Older (pre-C++11) code will use the virtual keyword as an inferior
  alternative annotation. For clarity, use exactly one of override,
  final, or virtual when declaring an override.

To better conform to these guidelines, the following constructs have
been rewritten:

- if a base class has a virtual destructor, then:
    virtual ~Foo();                   ->  ~Foo() override;
- virtual void Foo() override;        ->  void Foo() override;
- virtual void Foo() override final;  ->  void Foo() final;

This patch was automatically generated. The clang plugin can generate
fixit hints, which are suggested edits when it is 100% sure it knows how
to fix a problem. The hints from the clang plugin were applied to the
source tree using the tool in https://codereview.chromium.org/598073004.

BUG=417463
R=varkha@chromium.org

Review URL: https://codereview.chromium.org/681913002

Cr-Commit-Position: refs/heads/master@{#301501}

2dec45fb

Standardize usage of virtual/override/final specifiers. · 3f5cbabd

dcheng authored Oct 27, 2014

The Google C++ style guide states:

  Explicitly annotate overrides of virtual functions or virtual
  destructors with an override or (less frequently) final specifier.
  Older (pre-C++11) code will use the virtual keyword as an inferior
  alternative annotation. For clarity, use exactly one of override,
  final, or virtual when declaring an override.

To better conform to these guidelines, the following constructs have
been rewritten:

- if a base class has a virtual destructor, then:
    virtual ~Foo();                   ->  ~Foo() override;
- virtual void Foo() override;        ->  void Foo() override;
- virtual void Foo() override final;  ->  void Foo() final;

This patch was automatically generated. The clang plugin can generate
fixit hints, which are suggested edits when it is 100% sure it knows how
to fix a problem. The hints from the clang plugin were applied to the
source tree using the tool in https://codereview.chromium.org/598073004.

BUG=417463
R=sadrul@chromium.org

Review URL: https://codereview.chromium.org/681883002

Cr-Commit-Position: refs/heads/master@{#301500}

3f5cbabd

Standardize usage of virtual/override/final specifiers. · b1c24b60

dcheng authored Oct 27, 2014

The Google C++ style guide states:

  Explicitly annotate overrides of virtual functions or virtual
  destructors with an override or (less frequently) final specifier.
  Older (pre-C++11) code will use the virtual keyword as an inferior
  alternative annotation. For clarity, use exactly one of override,
  final, or virtual when declaring an override.

To better conform to these guidelines, the following constructs have
been rewritten:

- if a base class has a virtual destructor, then:
    virtual ~Foo();                   ->  ~Foo() override;
- virtual void Foo() override;        ->  void Foo() override;
- virtual void Foo() override final;  ->  void Foo() final;

This patch was automatically generated. The clang plugin can generate
fixit hints, which are suggested edits when it is 100% sure it knows how
to fix a problem. The hints from the clang plugin were applied to the
source tree using the tool in https://codereview.chromium.org/598073004.

BUG=417463
R=sadrul@chromium.org

Review URL: https://codereview.chromium.org/683553002

Cr-Commit-Position: refs/heads/master@{#301499}

b1c24b60

Standardize usage of virtual/override/final specifiers. · d002275e

dcheng authored Oct 27, 2014

The Google C++ style guide states:

  Explicitly annotate overrides of virtual functions or virtual
  destructors with an override or (less frequently) final specifier.
  Older (pre-C++11) code will use the virtual keyword as an inferior
  alternative annotation. For clarity, use exactly one of override,
  final, or virtual when declaring an override.

To better conform to these guidelines, the following constructs have
been rewritten:

- if a base class has a virtual destructor, then:
    virtual ~Foo();                   ->  ~Foo() override;
- virtual void Foo() override;        ->  void Foo() override;
- virtual void Foo() override final;  ->  void Foo() final;

This patch was automatically generated. The clang plugin can generate
fixit hints, which are suggested edits when it is 100% sure it knows how
to fix a problem. The hints from the clang plugin were applied to the
source tree using the tool in https://codereview.chromium.org/598073004.

BUG=417463
R=thestig@chromium.org

Review URL: https://codereview.chromium.org/679273002

Cr-Commit-Position: refs/heads/master@{#301498}

d002275e

Standardize usage of virtual/override/final specifiers. · 5e6a48d3

dcheng authored Oct 27, 2014

The Google C++ style guide states:

  Explicitly annotate overrides of virtual functions or virtual
  destructors with an override or (less frequently) final specifier.
  Older (pre-C++11) code will use the virtual keyword as an inferior
  alternative annotation. For clarity, use exactly one of override,
  final, or virtual when declaring an override.

To better conform to these guidelines, the following constructs have
been rewritten:

- if a base class has a virtual destructor, then:
    virtual ~Foo();                   ->  ~Foo() override;
- virtual void Foo() override;        ->  void Foo() override;
- virtual void Foo() override final;  ->  void Foo() final;

This patch was automatically generated. The clang plugin can generate
fixit hints, which are suggested edits when it is 100% sure it knows how
to fix a problem. The hints from the clang plugin were applied to the
source tree using the tool in https://codereview.chromium.org/598073004.

BUG=417463
R=skuhne@chromium.org

Review URL: https://codereview.chromium.org/685483004

Cr-Commit-Position: refs/heads/master@{#301497}

5e6a48d3

Standardize usage of virtual/override/final specifiers. · fbf9696f

dcheng authored Oct 27, 2014

The Google C++ style guide states:

  Explicitly annotate overrides of virtual functions or virtual
  destructors with an override or (less frequently) final specifier.
  Older (pre-C++11) code will use the virtual keyword as an inferior
  alternative annotation. For clarity, use exactly one of override,
  final, or virtual when declaring an override.

To better conform to these guidelines, the following constructs have
been rewritten:

- if a base class has a virtual destructor, then:
    virtual ~Foo();                   ->  ~Foo() override;
- virtual void Foo() override;        ->  void Foo() override;
- virtual void Foo() override final;  ->  void Foo() final;

This patch was automatically generated. The clang plugin can generate
fixit hints, which are suggested edits when it is 100% sure it knows how
to fix a problem. The hints from the clang plugin were applied to the
source tree using the tool in https://codereview.chromium.org/598073004.

BUG=417463
R=skuhne@chromium.org

Review URL: https://codereview.chromium.org/686593002

Cr-Commit-Position: refs/heads/master@{#301496}

fbf9696f

Revert unintended prevention of seeks on infinite duration media. · 56359cbf

dalecurtis authored Oct 27, 2014

Preserves the looping behavior for 200-type sources, while reverting
the disabling of seeks for "non-streaming" type sources which report
an infinite duration. This reverts the unintended behavior change
from http://crrev.com/298565

BUG=412562,427412
TEST=live player works again. LayoutTest forthcoming.

Review URL: https://codereview.chromium.org/684473002

Cr-Commit-Position: refs/heads/master@{#301495}

56359cbf

Temporarily excluding failing test on valgrind/drmemory bots · d68b1649

Mitsuru Oshima authored Oct 27, 2014

BUG=427729
TBR=lanwei@chromium.org

Review URL: https://codereview.chromium.org/680183003

Cr-Commit-Position: refs/heads/master@{#301494}

d68b1649

Update a bunch of OWNERS files. · 0ee290d0

ben authored Oct 27, 2014

Remove v2.

R=sky@chromium.org
BUG=

Review URL: https://codereview.chromium.org/682713003

Cr-Commit-Position: refs/heads/master@{#301493}

0ee290d0

Move app_installer into chromium. · 511a873f

jackhou authored Oct 27, 2014

This code was previously in
https://chrome-internal.googlesource.com/chrome-app-installer.git

We're moving it to chromium with the goal of having it
eventually built as part of Chrome releases.

The third_party code is used to extract the tags added
by dl.google.com. Omaha uses this mechanism to tag their
meta-installers.

BUG=341353

Review URL: https://codereview.chromium.org/423293004

Cr-Commit-Position: refs/heads/master@{#301492}

511a873f

Standardize usage of virtual/override/final specifiers. · 4c112747

dcheng authored Oct 27, 2014

The Google C++ style guide states:

  Explicitly annotate overrides of virtual functions or virtual
  destructors with an override or (less frequently) final specifier.
  Older (pre-C++11) code will use the virtual keyword as an inferior
  alternative annotation. For clarity, use exactly one of override,
  final, or virtual when declaring an override.

To better conform to these guidelines, the following constructs have
been rewritten:

- if a base class has a virtual destructor, then:
    virtual ~Foo();                   ->  ~Foo() override;
- virtual void Foo() override;        ->  void Foo() override;
- virtual void Foo() override final;  ->  void Foo() final;

This patch was automatically generated. The clang plugin can generate
fixit hints, which are suggested edits when it is 100% sure it knows how
to fix a problem. The hints from the clang plugin were applied to the
source tree using the tool in https://codereview.chromium.org/598073004.

BUG=417463
R=asvitkine@chromium.org

Review URL: https://codereview.chromium.org/679243002

Cr-Commit-Position: refs/heads/master@{#301491}

4c112747

27 Oct, 2014 27 commits

Standardize usage of virtual/override/final specifiers. · 1f4538e0

dcheng authored Oct 27, 2014

The Google C++ style guide states:

  Explicitly annotate overrides of virtual functions or virtual
  destructors with an override or (less frequently) final specifier.
  Older (pre-C++11) code will use the virtual keyword as an inferior
  alternative annotation. For clarity, use exactly one of override,
  final, or virtual when declaring an override.

To better conform to these guidelines, the following constructs have
been rewritten:

- if a base class has a virtual destructor, then:
    virtual ~Foo();                   ->  ~Foo() override;
- virtual void Foo() override;        ->  void Foo() override;
- virtual void Foo() override final;  ->  void Foo() final;

This patch was automatically generated. The clang plugin can generate
fixit hints, which are suggested edits when it is 100% sure it knows how
to fix a problem. The hints from the clang plugin were applied to the
source tree using the tool in https://codereview.chromium.org/598073004.

BUG=417463
R=derat@chromium.org

Review URL: https://codereview.chromium.org/680153002

Cr-Commit-Position: refs/heads/master@{#301490}

1f4538e0

· e19d49ab

Adam Langley authored Oct 27, 2014

net: add a batch of HSTS preloads.
Cr-Commit-Position: refs/heads/master@{#301489}

e19d49ab

MenuButtons enter Hover state upon Tap Down · c22434d2

jonross authored Oct 27, 2014

MenuButton will now respond to TAP_DOWN gestures, entering the Hover state. It will return to a normal state if the gesture is cancelled. Tap gestures that activate the menu will still cause it to enter a Pressed state.

This experiment is behind the flag switches::kEnableTouchFeedback

TEST=MenuButtonTest.TouchFeedbackDuringTap, MenuButtonTest.TouchFeedbackDuringTapCancel
BUG=398404

Review URL: https://codereview.chromium.org/674163003

Cr-Commit-Position: refs/heads/master@{#301488}

c22434d2

Refactor top_25 so only page class with custom Run.. logic is defined · 26757de9

nednguyen authored Oct 27, 2014

BUG=418375

Review URL: https://codereview.chromium.org/650293007

Cr-Commit-Position: refs/heads/master@{#301487}

26757de9

Cleanup: Remove unneeded chrome/common/pref_names.h includes. · 7e3b19da
thestig authored Oct 27, 2014
```
Review URL: https://codereview.chromium.org/674273002

Cr-Commit-Position: refs/heads/master@{#301486}
```
7e3b19da

net: add domain ID for Facebook. · fc62f189

Adam Langley authored Oct 27, 2014

Facebook domains were added with pinning in
https://codereview.chromium.org/673313002/. However, I omitted to add a new
domain ID for it. This resulted in it having an ID of zero.

The generation script has been updated to catch this in the future[1].

[1] https://github.com/agl/transport-security-state-generate/commit/641c7af7cac98a96386cd3fb3c4444316f8ea967

BUG=none
R=palmer@chromium.org

Review URL: https://codereview.chromium.org/673843003

Cr-Commit-Position: refs/heads/master@{#301485}

fc62f189

mac: Update metrics for Fullscreen styles. · b4159bc3

erikchen authored Oct 27, 2014

I removed the metric "OSX.Fullscreen.Enter" because the confusion it was
causing outweighted the additional information it provided.

It has been replaced by 3 metrics:
  - OSX.Fullscreen.Enter.Style
  - OSX.Fullscreen.Enter.WindowLocation
  - OSX.Settings.ScreensHaveSeparateSpaces

BUG=414527

Review URL: https://codereview.chromium.org/640053007

Cr-Commit-Position: refs/heads/master@{#301484}

b4159bc3

Standardize usage of virtual/override/final specifiers. · f599cb1f

dcheng authored Oct 27, 2014

The Google C++ style guide states:

  Explicitly annotate overrides of virtual functions or virtual
  destructors with an override or (less frequently) final specifier.
  Older (pre-C++11) code will use the virtual keyword as an inferior
  alternative annotation. For clarity, use exactly one of override,
  final, or virtual when declaring an override.

To better conform to these guidelines, the following constructs have
been rewritten:

- if a base class has a virtual destructor, then:
    virtual ~Foo();                   ->  ~Foo() override;
- virtual void Foo() override;        ->  void Foo() override;
- virtual void Foo() override final;  ->  void Foo() final;

This patch was automatically generated. The clang plugin can generate
fixit hints, which are suggested edits when it is 100% sure it knows how
to fix a problem. The hints from the clang plugin were applied to the
source tree using the tool in https://codereview.chromium.org/598073004.

BUG=417463
R=sadrul@chromium.org

Review URL: https://codereview.chromium.org/684463003

Cr-Commit-Position: refs/heads/master@{#301483}

f599cb1f

Standardize usage of virtual/override/final specifiers. · a0f10dd5

dcheng authored Oct 27, 2014

The Google C++ style guide states:

  Explicitly annotate overrides of virtual functions or virtual
  destructors with an override or (less frequently) final specifier.
  Older (pre-C++11) code will use the virtual keyword as an inferior
  alternative annotation. For clarity, use exactly one of override,
  final, or virtual when declaring an override.

To better conform to these guidelines, the following constructs have
been rewritten:

- if a base class has a virtual destructor, then:
    virtual ~Foo();                   ->  ~Foo() override;
- virtual void Foo() override;        ->  void Foo() override;
- virtual void Foo() override final;  ->  void Foo() final;

This patch was automatically generated. The clang plugin can generate
fixit hints, which are suggested edits when it is 100% sure it knows how
to fix a problem. The hints from the clang plugin were applied to the
source tree using the tool in https://codereview.chromium.org/598073004.

BUG=417463
R=benwells@chromium.org

Review URL: https://codereview.chromium.org/681053002

Cr-Commit-Position: refs/heads/master@{#301482}

a0f10dd5

[Sync] Fix bug where DeviceInfo is missing a backup timestamp · 44d30709

maniscalco authored Oct 27, 2014

Remove last_synced_time_ member variable from ProfileSyncService.  This
variable acted as a cache of the underlying pref.  However, it was not
properly cleared in ProfileSyncService::DisableForUser when the
associated pref was cleared.  This caused a bug where device info may
not have a backup timestamp.

BUG=427096

Review URL: https://codereview.chromium.org/660023003

Cr-Commit-Position: refs/heads/master@{#301481}

44d30709

Adding instrumentation to locate the source of jankiness. · 8ada724c

vadimt authored Oct 27, 2014

Mechanical change that adds instrumentation required to locate the source of jankiness (i.e. a long-running fragment of code executed as a part of the task that causes jank) in the code. See the bug for details on what kind of jank we are after.
A number of similar CLs were landed, and none of them caused issues. They've helped to find and fix janky code. The code of the instrumentation is highly optimized and is not expected to affect performance. The code simply creates a diagnostic task which is identical to ones created by PostTask or IPC message handlers.
Landing as TBR since this is a mechanical, safe and temporary change.

This CL instruments code invoked from URLRequestFileJob::DidOpen, which is responsible for 15.3 jph.

BUG=423948
TBR=mmenke@chromium.org

Review URL: https://codereview.chromium.org/675303004

Cr-Commit-Position: refs/heads/master@{#301480}

8ada724c

Standardize usage of virtual/override/final specifiers. · abd860e4

dcheng authored Oct 27, 2014

The Google C++ style guide states:

  Explicitly annotate overrides of virtual functions or virtual
  destructors with an override or (less frequently) final specifier.
  Older (pre-C++11) code will use the virtual keyword as an inferior
  alternative annotation. For clarity, use exactly one of override,
  final, or virtual when declaring an override.

To better conform to these guidelines, the following constructs have
been rewritten:

- if a base class has a virtual destructor, then:
    virtual ~Foo();                   ->  ~Foo() override;
- virtual void Foo() override;        ->  void Foo() override;
- virtual void Foo() override final;  ->  void Foo() final;

This patch was automatically generated. The clang plugin can generate
fixit hints, which are suggested edits when it is 100% sure it knows how
to fix a problem. The hints from the clang plugin were applied to the
source tree using the tool in https://codereview.chromium.org/598073004.

BUG=417463
R=thestig@chromium.org

Review URL: https://codereview.chromium.org/678803003

Cr-Commit-Position: refs/heads/master@{#301479}

abd860e4

Standardize usage of virtual/override/final specifiers. · 2f4c4b6f

dcheng authored Oct 27, 2014

The Google C++ style guide states:

  Explicitly annotate overrides of virtual functions or virtual
  destructors with an override or (less frequently) final specifier.
  Older (pre-C++11) code will use the virtual keyword as an inferior
  alternative annotation. For clarity, use exactly one of override,
  final, or virtual when declaring an override.

To better conform to these guidelines, the following constructs have
been rewritten:

- if a base class has a virtual destructor, then:
    virtual ~Foo();                   ->  ~Foo() override;
- virtual void Foo() override;        ->  void Foo() override;
- virtual void Foo() override final;  ->  void Foo() final;

This patch was automatically generated. The clang plugin can generate
fixit hints, which are suggested edits when it is 100% sure it knows how
to fix a problem. The hints from the clang plugin were applied to the
source tree using the tool in https://codereview.chromium.org/598073004.

BUG=417463
R=vasilii@chromium.org

Review URL: https://codereview.chromium.org/681043002

Cr-Commit-Position: refs/heads/master@{#301478}

2f4c4b6f

Fix pkg-config issue with cras for Chrome OS build. · 77287dc5

benchan authored Oct 27, 2014

BUG=None
TEST=Run `gn gen` with 'os="chromeos" use_cras=true'.

Review URL: https://codereview.chromium.org/682743003

Cr-Commit-Position: refs/heads/master@{#301477}

77287dc5

Remove //content/shell/layout_tests/. · 8194a9f9

peter authored Oct 27, 2014

The last change to the TestExpectations file was made in January 2013,
and nothing is referring to it (or this directory) anymore.

BUG=

Review URL: https://codereview.chromium.org/674193003

Cr-Commit-Position: refs/heads/master@{#301476}

8194a9f9

Cleanup: Remove some unneeded timer.h includes. · 9944ec3e

thestig authored Oct 27, 2014

Review URL: https://codereview.chromium.org/645343004

Cr-Commit-Position: refs/heads/master@{#301475}

9944ec3e

Revert "ozone: evdev: Handle mouse events" · ae2cd5b9

Antoine Labour authored Oct 27, 2014

This reverts commit e6e890a7.

Causes compile failures:
http://build.chromium.org/p/chromium.chromiumos/builders/Linux%20ChromiumOS%20Ozone%20Builder/builds/5856/steps/compile/logs/stdio

TBR=spang
BUG=

Review URL: https://codereview.chromium.org/682753005

Cr-Commit-Position: refs/heads/master@{#301474}

ae2cd5b9

remove DIR_LOCAL_APP_DATA_LOW from base. · 1b29da2e

cpu authored Oct 27, 2014

Not used except for cloud print.

BUG=426573
TBR=rvargas

Review URL: https://codereview.chromium.org/681533002

Cr-Commit-Position: refs/heads/master@{#301473}

1b29da2e

Remove proxy retry time condition from CORS bypass integration test. · 7e150a90

sclittle authored Oct 27, 2014

This fixes the failing CORS bypass telemetry test for the data reduction
proxy. The CORS bypass test doesn't need to care what kind of bypass
was caused, just that the CORS request was bypassed.

Also made VerifyProxyInfo resilient to the actual and expected proxy
lists being ordered differently.

BUG=423916

Review URL: https://codereview.chromium.org/663333004

Cr-Commit-Position: refs/heads/master@{#301472}

7e150a90

Made ChromeShellSyncTests run alongside the other instrumentation tests. · 94c8f1ad

mikecase authored Oct 27, 2014

The ChromeShellSyncTest tests have been running on some of the
chromium-fyi android bots. The tests have passed consistently for
several days and I am now moving them to run with the rest of the
instrumentation tests.

BUG=406538

Review URL: https://codereview.chromium.org/680573004

Cr-Commit-Position: refs/heads/master@{#301471}

94c8f1ad

Make IsProxyBypassed work when there are no bad proxies. · b904b15f

sclittle authored Oct 27, 2014

Currently, if there are no bad proxies, IsProxyBypassed will cause a
runtime error. This change makes it return (False, []) as expected.

BUG=427666

Review URL: https://codereview.chromium.org/664483004

Cr-Commit-Position: refs/heads/master@{#301470}

b904b15f

Update zero suggest flags to match experiments. · ad3bfefc

mariakhomenko authored Oct 27, 2014

BUG=324043

Review URL: https://codereview.chromium.org/676053002

Cr-Commit-Position: refs/heads/master@{#301469}

ad3bfefc

Add mojo_system_unittest back to valgrind bots, which was removed by accident... · 7f8433e2

oshima authored Oct 27, 2014

Add mojo_system_unittest back to valgrind bots, which was removed by accident in https://codereview.chromium.org/681493003

R=jamesr@chromium.org
NOTRY=true

Review URL: https://codereview.chromium.org/683493004

Cr-Commit-Position: refs/heads/master@{#301468}

7f8433e2

Remove page id from title updating. · c04f5375

avi authored Oct 27, 2014

BUG=407376
TEST=none

Review URL: https://codereview.chromium.org/683563003

Cr-Commit-Position: refs/heads/master@{#301467}

c04f5375

Standardize usage of virtual/override/final specifiers. · 02542c99

dcheng authored Oct 27, 2014

The Google C++ style guide states:

  Explicitly annotate overrides of virtual functions or virtual
  destructors with an override or (less frequently) final specifier.
  Older (pre-C++11) code will use the virtual keyword as an inferior
  alternative annotation. For clarity, use exactly one of override,
  final, or virtual when declaring an override.

To better conform to these guidelines, the following constructs have
been rewritten:

- if a base class has a virtual destructor, then:
    virtual ~Foo();                   ->  ~Foo() override;
- virtual void Foo() override;        ->  void Foo() override;
- virtual void Foo() override final;  ->  void Foo() final;

This patch was automatically generated. The clang plugin can generate
fixit hints, which are suggested edits when it is 100% sure it knows how
to fix a problem. The hints from the clang plugin were applied to the
source tree using the tool in https://codereview.chromium.org/598073004.

BUG=417463
R=pkasting@chromium.org

Review URL: https://codereview.chromium.org/680053003

Cr-Commit-Position: refs/heads/master@{#301466}

02542c99

ozone: evdev: Handle mouse events · e6e890a7

tiago.vignatti authored Oct 27, 2014

This CL renames KeyEventConverterEvdev to EventConverterEvdevImpl, adding mouse
support there. It adds converter for mouse events that handles move and button
events. This is useful for simple mouse testing and also systems that don't
want the complexity of gestures library.

I don't have a multipurpose input device just like described in
crbug.com/412996, but I believe this benefits the needed changes towards that
goal as well.

BUG=412996
TEST=Run chrome target on DRI platform on non-CrOS.

Review URL: https://codereview.chromium.org/677113002

Cr-Commit-Position: refs/heads/master@{#301465}

e6e890a7

Revert "Don't initialize Ozone platform if running unit tests with OSMesa" · cc39bb88

Antoine Labour authored Oct 27, 2014

This reverts commit b1dfa83e.

Broke Linux ChromiumOS Ozone Tests:
http://build.chromium.org/p/chromium.chromiumos/builders/Linux%20ChromiumOS%20Ozone%20Tests%20%281%29/builds/5338/steps/interactive_ui_tests/logs/stdio

TBR=gusfernandez@chromium.org
BUG=

Review URL: https://codereview.chromium.org/682853002

Cr-Commit-Position: refs/heads/master@{#301464}

cc39bb88