Move run_webkit_tests.* script into their new home.

Move run_webkit_tests.* script into their new home.

As we are removing webkit/ glue, we need a new home for these scripts.

BUG=338338
TEST=None
R=dpranke@chromium.org

Committed: https://crrev.com/a16e8bc1de2136c13428818295663cd46681e5e8
Cr-Commit-Position: refs/heads/master@{#299051}

[tfarina, 2014-10-06 00:25:40]

Patchset #3 (id:40001) has been deleted

[tfarina, 2014-10-06 00:25:45]

Patchset #2 (id:20001) has been deleted

[tfarina, 2014-10-06 00:25:53]

Patchset #1 (id:1) has been deleted

[tfarina, 2014-10-06 00:27:51]

Is this OK?

Is this final location ok?

[dcheng, 2014-10-06 00:28:36]

On 2014/10/06 00:25:53, tfarina wrote:
> Patchset #1 (id:1) has been deleted

Maybe before outright deleting it, it would be nice to have a pointer from the
old to the new script for a few days?

[Dirk Pranke, 2014-10-06 00:32:58]

dpranke@chromium.org changed reviewers:
+ eseidel@chromium.org

[Dirk Pranke, 2014-10-06 00:32:59]

I defer this to Eric to sign off on, to make sure it won't mess with the plan to
merge the repos.

[tfarina, 2014-10-06 00:33:32]

On 2014/10/06 00:28:36, dcheng wrote:
> On 2014/10/06 00:25:53, tfarina wrote:
> > Patchset #1 (id:1) has been deleted
> 
> Maybe before outright deleting it, it would be nice to have a pointer from the
> old to the new script for a few days?

By a pointer you mean 'print a message when the user runs run_webkit_tests.py
warning that it will be removed in a few days and pointing to the new location'?

[jamesr, 2014-10-06 01:00:27]

I suspect having files in the blink/ subdirectory will make merging the
repo in to here more difficult.

To unsubscribe from this group and stop receiving emails from it, send an email
to chromium-reviews+unsubscribe@chromium.org.

[eseidel, 2014-10-06 16:53:23]

It might.  We can also just move them out of the way before we dcommit all of
WebKit into /blink

[eseidel, 2014-10-06 19:14:39]

The CQ bit was checked by eseidel@chromium.org

[eseidel, 2014-10-06 19:14:39]

lgtm

I doubt this matters either way.

[commit-bot: I haz the power, 2014-10-06 19:17:11]

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

[commit-bot: I haz the power, 2014-10-06 19:34:19]

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

[commit-bot: I haz the power, 2014-10-06 19:34:20]

Try jobs failed on following builders:
  chromium_presubmit on tryserver.chromium.linux
(http://build.chromium.org/p/tryserver.chromium.linux/builders/chromium_presub...)

[tfarina, 2014-10-06 20:55:01]

Thanks Eric.

Dirk, could you approve for webkit/tools/layout_tests/?

[Dirk Pranke, 2014-10-06 21:05:34]

On 2014/10/06 20:55:01, tfarina wrote:
> Thanks Eric.
> 
> Dirk, could you approve for webkit/tools/layout_tests/?

lgtm

[Dirk Pranke, 2014-10-06 21:08:17]

On 2014/10/06 21:05:34, Dirk Pranke wrote:
> On 2014/10/06 20:55:01, tfarina wrote:
> > Thanks Eric.
> > 
> > Dirk, could you approve for webkit/tools/layout_tests/?
> 
> lgtm

Oh, but looking at this made me realize that you're deleting OWNERS -- which is
fine -- but webkit/tools/layout_test/OWNERS had a blanket "*" entry so that
anyone could approve changes to webkit/toolss/layout_test/test_expectations* ,
and the new location (content/tests/test_expectations*) does *not* have that
approval.

I'll post a separate CL to add that.

[Dirk Pranke, 2014-10-06 21:12:31]

On 2014/10/06 21:08:17, Dirk Pranke wrote:
> Oh, but looking at this made me realize that you're deleting OWNERS --
which is
> fine -- but webkit/tools/layout_test/OWNERS had a blanket "*" entry so that
> anyone could approve changes to webkit/toolss/layout_test/test_expectations* ,
> and the new location (content/tests/test_expectations*) does *not* have that
> approval.
> 
> I'll post a separate CL to add that.

CL posted to https://codereview.chromium.org/629333002/.

[dcheng, 2014-10-08 01:42:38]

On 2014/10/06 at 00:33:32, tfarina wrote:
> On 2014/10/06 00:28:36, dcheng wrote:
> > On 2014/10/06 00:25:53, tfarina wrote:
> > > Patchset #1 (id:1) has been deleted
> > 
> > Maybe before outright deleting it, it would be nice to have a pointer from
the
> > old to the new script for a few days?
> 
> By a pointer you mean 'print a message when the user runs run_webkit_tests.py
warning that it will be removed in a few days and pointing to the new location'?

Guess I got dropped from the replies. But yes, this is what I meant. I suppose
it'll be fine without it though.

[tfarina, 2014-10-10 02:07:19]

The CQ bit was checked by tfarina@chromium.org

[commit-bot: I haz the power, 2014-10-10 02:09:01]

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

[commit-bot: I haz the power, 2014-10-10 02:18:43]

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

[commit-bot: I haz the power, 2014-10-10 02:18:44]

Try jobs failed on following builders:
  mac_gpu_triggered_tests on tryserver.chromium.gpu
(http://build.chromium.org/p/tryserver.chromium.gpu/builders/mac_gpu_triggered...)
  chromium_presubmit on tryserver.chromium.linux
(http://build.chromium.org/p/tryserver.chromium.linux/builders/chromium_presub...)

[tfarina, 2014-10-10 02:34:06]

The CQ bit was checked by tfarina@chromium.org

[commit-bot: I haz the power, 2014-10-10 02:34:55]

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

[commit-bot: I haz the power, 2014-10-10 03:11:40]

Committed patchset #3 (id:280001)

[commit-bot: I haz the power, 2014-10-10 03:12:22]

Patchset 3 (id:??) landed as
https://crrev.com/a16e8bc1de2136c13428818295663cd46681e5e8
Cr-Commit-Position: refs/heads/master@{#299051}