Roll third_party/typ to 0.9.5.

Roll third_party/typ to 0.9.5.

This pulls in two minor bug fixes and a new feature: support for
sharding via --shard-index and --total-shards.

R=nednguyen@chromium.org
BUG=620959
Committed: https://crrev.com/52bb9d4d20c7363cb88f51cf0860362f303a228a
Cr-Commit-Position: refs/heads/master@{#400721}

[Dirk Pranke, 2016-06-19 23:32:26]

The CQ bit was checked by dpranke@chromium.org to run a CQ dry run

[commit-bot: I haz the power, 2016-06-19 23:32:39]

Dry run: CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/2077273002/1

[commit-bot: I haz the power, 2016-06-20 00:08:16]

The CQ bit was unchecked by commit-bot@chromium.org

[commit-bot: I haz the power, 2016-06-20 00:08:17]

Dry run: This issue passed the CQ dry run.

[nednguyen, 2016-06-20 04:32:06]

On 2016/06/20 00:08:17, commit-bot: I haz the power wrote:
> Dry run: This issue passed the CQ dry run.

lgtm

Thanks Dirk!

[nednguyen, 2016-06-20 04:33:30]

nednguyen@google.com changed reviewers:
+ nednguyen@google.com

[nednguyen, 2016-06-20 04:33:31]

https://codereview.chromium.org/2077273002/diff/1/third_party/typ/typ/host.py
File third_party/typ/typ/host.py (right):

https://codereview.chromium.org/2077273002/diff/1/third_party/typ/typ/host.py...
third_party/typ/typ/host.py:60: sys.path.insert(0, absolute_path)
note that this can be disrupted for some project in chromium. When I rolled
this, I have to telemetry's page_sets directory to test_page_sets to avoid
naming conflict with the same folder name in content/test/gpu

[Dirk Pranke, 2016-06-20 16:19:26]

https://codereview.chromium.org/2077273002/diff/1/third_party/typ/typ/host.py
File third_party/typ/typ/host.py (right):

https://codereview.chromium.org/2077273002/diff/1/third_party/typ/typ/host.py...
third_party/typ/typ/host.py:60: sys.path.insert(0, absolute_path)
On 2016/06/20 04:33:30, nednguyen wrote:
> note that this can be disrupted for some project in chromium. When I rolled
> this, I have to telemetry's page_sets directory to test_page_sets to avoid
> naming conflict with the same folder name in content/test/gpu

Can you explain further? Are you saying typ shouldn't do this, or that add to
back would've been better, or something else?

[nednguyen, 2016-06-20 17:29:59]

https://codereview.chromium.org/2077273002/diff/1/third_party/typ/typ/host.py
File third_party/typ/typ/host.py (right):

https://codereview.chromium.org/2077273002/diff/1/third_party/typ/typ/host.py...
third_party/typ/typ/host.py:60: sys.path.insert(0, absolute_path)
On 2016/06/20 16:19:26, Dirk Pranke wrote:
> On 2016/06/20 04:33:30, nednguyen wrote:
> > note that this can be disrupted for some project in chromium. When I rolled
> > this, I have to telemetry's page_sets directory to test_page_sets to avoid
> > naming conflict with the same folder name in content/test/gpu
> 
> Can you explain further? Are you saying typ shouldn't do this, or that add to
> back would've been better, or something else?

Adding this is good for the reason in https://github.com/dpranke/typ/issues/3.
However, some of the current tests may rely on this behavior & will fail with
this change.

When I roll this change in https://codereview.chromium.org/2072163002/, it
turned out that telemetry has a directory named page_sets which is the same as
content/test/gpu, and that blocked our catapult roll. I had to do a subsequent
fix in https://codereview.chromium.org/2072373002/

I would vote for try to land this, but keep an eye on potential breakages.

[Dirk Pranke, 2016-06-20 17:54:59]

On 2016/06/20 17:29:59, nednguyen wrote:
> https://codereview.chromium.org/2077273002/diff/1/third_party/typ/typ/host.py
> File third_party/typ/typ/host.py (right):
> 
>
https://codereview.chromium.org/2077273002/diff/1/third_party/typ/typ/host.py...
> third_party/typ/typ/host.py:60: sys.path.insert(0, absolute_path)
> On 2016/06/20 16:19:26, Dirk Pranke wrote:
> > On 2016/06/20 04:33:30, nednguyen wrote:
> > > note that this can be disrupted for some project in chromium. When I
rolled
> > > this, I have to telemetry's page_sets directory to test_page_sets to avoid
> > > naming conflict with the same folder name in content/test/gpu
> > 
> > Can you explain further? Are you saying typ shouldn't do this, or that add
to
> > back would've been better, or something else?
> 
> Adding this is good for the reason in https://github.com/dpranke/typ/issues/3.
> However, some of the current tests may rely on this behavior & will fail with
> this change.
> 
> When I roll this change in https://codereview.chromium.org/2072163002/, it
> turned out that telemetry has a directory named page_sets which is the same as
> content/test/gpu, and that blocked our catapult roll. I had to do a subsequent
> fix in https://codereview.chromium.org/2072373002/
> 
> I would vote for try to land this, but keep an eye on potential breakages.

Okay.

[Dirk Pranke, 2016-06-20 17:55:03]

The CQ bit was checked by dpranke@chromium.org

[commit-bot: I haz the power, 2016-06-20 17:55:26]

CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/2077273002/1

[commit-bot: I haz the power, 2016-06-20 18:01:06]

Committed patchset #1 (id:1)

[commit-bot: I haz the power, 2016-06-20 18:04:59]

Description was changed from

==========
Roll third_party/typ to 0.9.5.

This pulls in two minor bug fixes and a new feature: support for
sharding via --shard-index and --total-shards.

R=nednguyen@chromium.org
BUG=620959
==========

to

==========
Roll third_party/typ to 0.9.5.

This pulls in two minor bug fixes and a new feature: support for
sharding via --shard-index and --total-shards.

R=nednguyen@chromium.org
BUG=620959

Committed: https://crrev.com/52bb9d4d20c7363cb88f51cf0860362f303a228a
Cr-Commit-Position: refs/heads/master@{#400721}
==========

[commit-bot: I haz the power, 2016-06-20 18:05:00]

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