Add pdf_unittests target.

Add pdf_unittests target.

Needs for https://codereview.chromium.org/2349753003/

Committed: https://crrev.com/0c349265b7e348208ae854da696be2f69b7d3f9f
Cr-Commit-Position: refs/heads/master@{#428066}

[snake, 2016-10-27 11:07:46]

Description was changed from

==========
Add pdf_unittests target.

Needs for https://codereview.chromium.org/2349753003/
==========

to

==========
Add pdf_unittests target.

Needs for https://codereview.chromium.org/2349753003/
==========

[snake, 2016-10-27 11:07:47]

art-snake@yandex-team.ru changed reviewers:
+ thestig@chromium.org

[snake, 2016-10-27 12:09:01]

> If we take smaller steps instead a bigger leap, we may have been
> able to avoid this. e.g.

> 1) Add the pdf_unittests build target, with some simple tests in one CL.
This CL
> 2) Change build bot configs to build and run pdf_unittests. (Requires
> maybe a few CLs to do the bot configuration?)
How I can do this? 
Manually add target into all(or specific?) src/testing/buildbot/*.json ?
Should I do this in this CL?

> 3) Land the rest of this CL. At which point, there will actually be
> proper coverage for pdf_unittests.

Should I create new CL on this step, or reopen old?

[Lei Zhang, 2016-10-27 16:23:51]

The CQ bit was checked by thestig@chromium.org

[Lei Zhang, 2016-10-27 16:23:51]

lgtm

[commit-bot: I haz the power, 2016-10-27 16:24:19]

CQ is trying da patch. Follow status at
 
https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...

[commit-bot: I haz the power, 2016-10-27 17:22:10]

Description was changed from

==========
Add pdf_unittests target.

Needs for https://codereview.chromium.org/2349753003/
==========

to

==========
Add pdf_unittests target.

Needs for https://codereview.chromium.org/2349753003/
==========

[commit-bot: I haz the power, 2016-10-27 17:22:11]

Committed patchset #1 (id:1)

[snake, 2016-10-27 17:23:10]

On 2016/10/27 17:22:11, commit-bot: I haz the power wrote:
> Committed patchset #1 (id:1)

What should I do next?
Manually add target into all(or specific?) testing/buildbot/*.json ?

[commit-bot: I haz the power, 2016-10-27 17:31:15]

Description was changed from

==========
Add pdf_unittests target.

Needs for https://codereview.chromium.org/2349753003/
==========

to

==========
Add pdf_unittests target.

Needs for https://codereview.chromium.org/2349753003/

Committed: https://crrev.com/0c349265b7e348208ae854da696be2f69b7d3f9f
Cr-Commit-Position: refs/heads/master@{#428066}
==========

[commit-bot: I haz the power, 2016-10-27 17:31:16]

Patchset 1 (id:??) landed as
https://crrev.com/0c349265b7e348208ae854da696be2f69b7d3f9f
Cr-Commit-Position: refs/heads/master@{#428066}

[Lei Zhang, 2016-10-27 18:43:23]

On 2016/10/27 17:23:10, snake wrote:
> On 2016/10/27 17:22:11, commit-bot: I haz the power wrote:
> > Committed patchset #1 (id:1)
> 
> What should I do next?
> Manually add target into all(or specific?) testing/buildbot/*.json ?

Looks like you did that. I asked Dirk on the other CL about try bot configs.