updated w3c import script to align with the new css test repo structure

updated w3c import script to align with the new css test repo structure as
described here: 
http://lists.w3.org/Archives/Public/public-css-testsuite/2014May/0000.html

Committed: https://src.chromium.org/viewvc/blink?view=rev&revision=180118

[Dirk Pranke, 2014-08-12 00:50:23]

The changes to w3c_importer.py lgtm (assuming my comment is correct).

We should separate that change from the change to W3CImportExpectations, and
have the latter change be part of a series of CLs necessary to update the repos
as documented in http://www.chromium.org/blink/importing-the-w3c-tests .

I suspect you're getting the presubmit errors because you are pointing at a
tip-of-tree w3c repo rather than the pinned versions we normally pull in. Is
that possible?

https://codereview.chromium.org/311673002/diff/1/Tools/Scripts/webkitpy/w3c/t...
File Tools/Scripts/webkitpy/w3c/test_importer.py (left):

https://codereview.chromium.org/311673002/diff/1/Tools/Scripts/webkitpy/w3c/t...
Tools/Scripts/webkitpy/w3c/test_importer.py:205: DIRS_TO_SKIP = ('.git', '.hg',
'data', 'archive', 'incoming')
so, data, archive and incoming don't exist on tip-of-tree in the github repos
any more?

[rhauck, 2014-08-12 20:21:09]

On 2014/08/12 00:50:23, Dirk Pranke wrote:
> The changes to w3c_importer.py lgtm (assuming my comment is correct).
> 
> We should separate that change from the change to W3CImportExpectations, and
> have the latter change be part of a series of CLs necessary to update the
repos
> as documented in http://www.chromium.org/blink/importing-the-w3c-tests .
> 

Ok, I removed it from this patch and will handle it separately as you suggest
following the (scary) docs. :)

> I suspect you're getting the presubmit errors because you are pointing at a
> tip-of-tree w3c repo rather than the pinned versions we normally pull in. Is
> that possible?
> 
>
https://codereview.chromium.org/311673002/diff/1/Tools/Scripts/webkitpy/w3c/t...
> File Tools/Scripts/webkitpy/w3c/test_importer.py (left):
> 
>
https://codereview.chromium.org/311673002/diff/1/Tools/Scripts/webkitpy/w3c/t...
> Tools/Scripts/webkitpy/w3c/test_importer.py:205: DIRS_TO_SKIP = ('.git',
'.hg',
> 'data', 'archive', 'incoming')
> so, data, archive and incoming don't exist on tip-of-tree in the github repos
> any more?

Yes, that's correct.

[rhauck, 2014-08-12 20:21:20]

The CQ bit was checked by rhauck@adobe.com

[commit-bot: I haz the power, 2014-08-12 20:21:42]

CQ is trying da patch. Follow status at
 https://chromium-status.appspot.com/cq/rhauck@adobe.com/311673002/20001

[Dirk Pranke, 2014-08-12 20:26:22]

The CQ bit was unchecked by dpranke@chromium.org

[Dirk Pranke, 2014-08-12 20:27:01]

On 2014/08/12 20:21:42, I haz the power (commit-bot) wrote:
> CQ is trying da patch. Follow status at
>  https://chromium-status.appspot.com/cq/rhauck@adobe.com/311673002/20001

I unchecked the CQ box; please update the description and re-submit, so that we
don't get all of that text committed that no longer matches the actual change.

[rhauck, 2014-08-12 20:32:57]

On 2014/08/12 20:27:01, Dirk Pranke wrote:
> On 2014/08/12 20:21:42, I haz the power (commit-bot) wrote:
> > CQ is trying da patch. Follow status at
> >  https://chromium-status.appspot.com/cq/rhauck@adobe.com/311673002/20001
> 
> I unchecked the CQ box; please update the description and re-submit, so that
we
> don't get all of that text committed that no longer matches the actual change.

Ok, done.  Is it ok to check the CQ box now?

[Dirk Pranke, 2014-08-12 20:36:32]

On 2014/08/12 20:32:57, rhauck wrote:
> On 2014/08/12 20:27:01, Dirk Pranke wrote:
> > On 2014/08/12 20:21:42, I haz the power (commit-bot) wrote:
> > > CQ is trying da patch. Follow status at
> > >  https://chromium-status.appspot.com/cq/rhauck@adobe.com/311673002/20001
> > 
> > I unchecked the CQ box; please update the description and re-submit, so that
> we
> > don't get all of that text committed that no longer matches the actual
change.
> 
> Ok, done.  Is it ok to check the CQ box now?

The description still reads a bit too much like an email too me rather than a
commit to the repo :).

But, yes, you can check the CQ again when you're happy w/ the text.

[rhauck, 2014-08-12 20:54:13]

The CQ bit was checked by rhauck@adobe.com

[rhauck, 2014-08-12 20:54:18]

The CQ bit was unchecked by rhauck@adobe.com

[rhauck, 2014-08-12 20:54:39]

The CQ bit was checked by rhauck@adobe.com

[commit-bot: I haz the power, 2014-08-12 20:56:42]

CQ is trying da patch. Follow status at
 https://chromium-status.appspot.com/cq/rhauck@adobe.com/311673002/20001

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

FYI, CQ is re-trying this CL (attempt #1).
The failing builders are:
  win_blink_rel on tryserver.blink
(http://build.chromium.org/p/tryserver.blink/builders/win_blink_rel/builds/22383)

[commit-bot: I haz the power, 2014-08-12 23:17:31]

Change committed as 180118