<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
<!DOCTYPE bugzilla SYSTEM "https://bugs.webkit.org/page.cgi?id=bugzilla.dtd">

<bugzilla version="5.0.4.1"
          urlbase="https://bugs.webkit.org/"
          
          maintainer="admin@webkit.org"
>

    <bug>
          <bug_id>60373</bug_id>
          
          <creation_ts>2011-05-06 09:17:03 -0700</creation_ts>
          <short_desc>check-webkit-style / TestExpectationChecker doesn&apos;t catch all parse errors in test_expectations.txt</short_desc>
          <delta_ts>2011-05-09 13:23:50 -0700</delta_ts>
          <reporter_accessible>1</reporter_accessible>
          <cclist_accessible>1</cclist_accessible>
          <classification_id>1</classification_id>
          <classification>Unclassified</classification>
          <product>WebKit</product>
          <component>Tools / Tests</component>
          <version>528+ (Nightly build)</version>
          <rep_platform>Unspecified</rep_platform>
          <op_sys>Unspecified</op_sys>
          <bug_status>RESOLVED</bug_status>
          <resolution>DUPLICATE</resolution>
          <dup_id>60466</dup_id>
          
          <bug_file_loc></bug_file_loc>
          <status_whiteboard></status_whiteboard>
          <keywords></keywords>
          <priority>P2</priority>
          <bug_severity>Normal</bug_severity>
          <target_milestone>---</target_milestone>
          
          
          <everconfirmed>1</everconfirmed>
          <reporter name="Adrienne Walker">enne</reporter>
          <assigned_to name="Nobody">webkit-unassigned</assigned_to>
          <cc>abarth</cc>
    
    <cc>dpranke</cc>
    
    <cc>enne</cc>
    
    <cc>levin</cc>
          

      

      

      

          <comment_sort_order>oldest_to_newest</comment_sort_order>  
          <long_desc isprivate="0" >
    <commentid>399545</commentid>
    <comment_count>0</comment_count>
    <who name="Adrienne Walker">enne</who>
    <bug_when>2011-05-06 09:17:03 -0700</bug_when>
    <thetext>It&apos;s unfortunate that it&apos;s so easy to check in a test_expectations.txt file that doesn&apos;t work either due to a typo or due to two rules that conflict with each other in specificity.  It&apos;d be nice if folks were warned that they were about to do such a thing.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>399562</commentid>
    <comment_count>1</comment_count>
    <who name="Adam Barth">abarth</who>
    <bug_when>2011-05-06 09:37:36 -0700</bug_when>
    <thetext>Another approach is to simply test_expectations to the point where it cannot have parse errors.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>399563</commentid>
    <comment_count>2</comment_count>
    <who name="Adrienne Walker">enne</who>
    <bug_when>2011-05-06 09:39:20 -0700</bug_when>
    <thetext>(In reply to comment #1)
&gt; Another approach is to simply test_expectations to the point where it cannot have parse errors.

This bug was prompted by http://trac.webkit.org/changeset/85950, which fixed what was called a parse error, but it was really a cuplicate expectation where one was more specific than the other.

On further inspection, it looks like check-webkit-style will complain about &quot;duplicate or ambiguous expectation&quot; but only if both offending lines are in the patch.  Maybe it needs to consider the whole file?</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>399564</commentid>
    <comment_count>3</comment_count>
    <who name="Adam Barth">abarth</who>
    <bug_when>2011-05-06 09:41:53 -0700</bug_when>
    <thetext>I don&apos;t believe it is possible to have parse errors in the Skipped files, which are another approach to the same problem.  Yes, I know Skipped files do not have all the features of test_expectations.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>399589</commentid>
    <comment_count>4</comment_count>
    <who name="David Levin">levin</who>
    <bug_when>2011-05-06 10:07:07 -0700</bug_when>
    <thetext>(In reply to comment #2)
&gt; (In reply to comment #1)
&gt; &gt; Another approach is to simply test_expectations to the point where it cannot have parse errors.
&gt; 
&gt; This bug was prompted by http://trac.webkit.org/changeset/85950, which fixed what was called a parse error, but it was really a cuplicate expectation where one was more specific than the other.
&gt; 
&gt; On further inspection, it looks like check-webkit-style will complain about &quot;duplicate or ambiguous expectation&quot; but only if both offending lines are in the patch.  Maybe it needs to consider the whole file?

In general, check-webkit-style only complains about the line that you changed. However, I&apos;m sure one could change this for a particular checker.

Patches welcome :).</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>399619</commentid>
    <comment_count>5</comment_count>
    <who name="Dirk Pranke">dpranke</who>
    <bug_when>2011-05-06 10:39:34 -0700</bug_when>
    <thetext>I think this should probably be merged into bug 51548, and I agree that the checker needs to consider the whole file, not just the lines that are modified.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>400707</commentid>
    <comment_count>6</comment_count>
    <who name="David Levin">levin</who>
    <bug_when>2011-05-09 13:23:50 -0700</bug_when>
    <thetext>This particular issue (of filtering errors) came up for another checker as well, so I&apos;m fixing both in one bug.

*** This bug has been marked as a duplicate of bug 60466 ***</thetext>
  </long_desc>
      
      

    </bug>

</bugzilla>