<?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>72001</bug_id>
          
          <creation_ts>2011-11-09 23:39:08 -0800</creation_ts>
          <short_desc>[Chromium] only run media GPU layout tests on platforms supporting accelerated compositing</short_desc>
          <delta_ts>2011-11-10 18:05:06 -0800</delta_ts>
          <reporter_accessible>1</reporter_accessible>
          <cclist_accessible>1</cclist_accessible>
          <classification_id>1</classification_id>
          <classification>Unclassified</classification>
          <product>WebKit</product>
          <component>New Bugs</component>
          <version>528+ (Nightly build)</version>
          <rep_platform>Unspecified</rep_platform>
          <op_sys>Unspecified</op_sys>
          <bug_status>RESOLVED</bug_status>
          <resolution>FIXED</resolution>
          
          
          <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="Andrew Scherkus">scherkus</reporter>
          <assigned_to name="Andrew Scherkus">scherkus</assigned_to>
          <cc>abarth</cc>
    
    <cc>dglazkov</cc>
    
    <cc>dpranke</cc>
    
    <cc>jamesr</cc>
    
    <cc>ojan</cc>
    
    <cc>tony</cc>
    
    <cc>webkit.review.bot</cc>
          

      

      

      

          <comment_sort_order>oldest_to_newest</comment_sort_order>  
          <long_desc isprivate="0" >
    <commentid>499682</commentid>
    <comment_count>0</comment_count>
    <who name="Andrew Scherkus">scherkus</who>
    <bug_when>2011-11-09 23:39:08 -0800</bug_when>
    <thetext>[Chromium] only run media GPU layout tests on platforms supporting accelerated compositing</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>499686</commentid>
    <comment_count>1</comment_count>
      <attachid>114443</attachid>
    <who name="Andrew Scherkus">scherkus</who>
    <bug_when>2011-11-09 23:41:46 -0800</bug_when>
    <thetext>Created attachment 114443
Patch</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>499688</commentid>
    <comment_count>2</comment_count>
    <who name="Andrew Scherkus">scherkus</who>
    <bug_when>2011-11-09 23:44:13 -0800</bug_when>
    <thetext>Reason being that the following line in test_expectations.txt:
WONTFIX SKIP GPU GPU-CG LEOPARD : media = PASS TIMEOUT FAIL

...doesn&apos;t seem to do the trick with respect to skipping the tests. Furthermore if I&apos;ve been debugging the layout test results correctly it also looks like it&apos;s marking all media tests on 10.5 (non-GPU) as PASS/FAIL.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>500003</commentid>
    <comment_count>3</comment_count>
    <who name="Tony Chang">tony</who>
    <bug_when>2011-11-10 09:36:33 -0800</bug_when>
    <thetext>(In reply to comment #2)
&gt; Reason being that the following line in test_expectations.txt:
&gt; WONTFIX SKIP GPU GPU-CG LEOPARD : media = PASS TIMEOUT FAIL
&gt; 
&gt; ...doesn&apos;t seem to do the trick with respect to skipping the tests. Furthermore if I&apos;ve been debugging the layout test results correctly it also looks like it&apos;s marking all media tests on 10.5 (non-GPU) as PASS/FAIL.

Can we figure out why the above doesn&apos;t work?</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>500034</commentid>
    <comment_count>4</comment_count>
    <who name="Andrew Scherkus">scherkus</who>
    <bug_when>2011-11-10 10:33:04 -0800</bug_when>
    <thetext>(In reply to comment #3)
&gt; (In reply to comment #2)
&gt; &gt; Reason being that the following line in test_expectations.txt:
&gt; &gt; WONTFIX SKIP GPU GPU-CG LEOPARD : media = PASS TIMEOUT FAIL
&gt; &gt; 
&gt; &gt; ...doesn&apos;t seem to do the trick with respect to skipping the tests. Furthermore if I&apos;ve been debugging the layout test results correctly it also looks like it&apos;s marking all media tests on 10.5 (non-GPU) as PASS/FAIL.
&gt; 
&gt; Can we figure out why the above doesn&apos;t work?

Turns out it _does_ work but that more-specific expectations will cause the test to run on 10.5 GPU.

Take a look at flakiness results for media/audio-controls-rendering.html:
http://test-results.appspot.com/dashboards/flakiness_dashboard.html#group=%40ToT%20GPU%20Mesa%20-%20chromium.org&amp;tests=media%2Faudio-controls-rendering&amp;showExpectations=true

It was previously marked as:
BUGWK70748 CPU : media/audio-controls-rendering.html = IMAGE

...which caused it to override the SKIP and start running on Mac 10.5 GPU. After rebaselining and removing that expectation the test is now skipped again.

Anyone know if that&apos;s the intended behaviour?</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>500039</commentid>
    <comment_count>5</comment_count>
    <who name="Ojan Vafai">ojan</who>
    <bug_when>2011-11-10 10:37:32 -0800</bug_when>
    <thetext>It is certainly the intended behavior that more specific listings override less specific ones. We could take a queue from CSS and add something like &quot;!important&quot; lol.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>500041</commentid>
    <comment_count>6</comment_count>
    <who name="Andrew Scherkus">scherkus</who>
    <bug_when>2011-11-10 10:40:08 -0800</bug_when>
    <thetext>(In reply to comment #5)
&gt; It is certainly the intended behavior that more specific listings override less specific ones. We could take a queue from CSS and add something like &quot;!important&quot; lol.

Yeah that&apos;s what I figured and certainly makes sense to me!

So... are we happy with my patch or should I investigate a different avenue?

Having the tests potentially run isn&apos;t fun because it generates noise on the flakiness dashboard as well as increases test cycle time.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>500043</commentid>
    <comment_count>7</comment_count>
    <who name="Tony Chang">tony</who>
    <bug_when>2011-11-10 10:40:26 -0800</bug_when>
    <thetext>This specific case seems like a bug since the SKIP line refers to GPU and the more specific line refers to CPU.  I wouldn&apos;t expect
  CPU : media/audio-controls-rendering.html = IMAGE
to override
  WONTFIX SKIP GPU GPU-CG LEOPARD : media = PASS TIMEOUT FAIL</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>500046</commentid>
    <comment_count>8</comment_count>
    <who name="Andrew Scherkus">scherkus</who>
    <bug_when>2011-11-10 10:44:29 -0800</bug_when>
    <thetext>(In reply to comment #7)
&gt; This specific case seems like a bug since the SKIP line refers to GPU and the more specific line refers to CPU.  I wouldn&apos;t expect
&gt;   CPU : media/audio-controls-rendering.html = IMAGE
&gt; to override
&gt;   WONTFIX SKIP GPU GPU-CG LEOPARD : media = PASS TIMEOUT FAIL

Check out the diff:
https://trac.webkit.org/changeset/99789/trunk/LayoutTests/platform/chromium/test_expectations.txt

It looks like it was listed as:
BUGWK70748 CPU : media/audio-controls-rendering.html = IMAGE 
BUGWK70748 GPU : media/audio-controls-rendering.html = IMAGE 

So in this case I guess GPU was being overridden.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>500048</commentid>
    <comment_count>9</comment_count>
    <who name="Tony Chang">tony</who>
    <bug_when>2011-11-10 10:48:28 -0800</bug_when>
    <thetext>(In reply to comment #8)
&gt; (In reply to comment #7)
&gt; &gt; This specific case seems like a bug since the SKIP line refers to GPU and the more specific line refers to CPU.  I wouldn&apos;t expect
&gt; &gt;   CPU : media/audio-controls-rendering.html = IMAGE
&gt; &gt; to override
&gt; &gt;   WONTFIX SKIP GPU GPU-CG LEOPARD : media = PASS TIMEOUT FAIL
&gt; 
&gt; Check out the diff:
&gt; https://trac.webkit.org/changeset/99789/trunk/LayoutTests/platform/chromium/test_expectations.txt
&gt; 
&gt; It looks like it was listed as:
&gt; BUGWK70748 CPU : media/audio-controls-rendering.html = IMAGE 
&gt; BUGWK70748 GPU : media/audio-controls-rendering.html = IMAGE 
&gt; 
&gt; So in this case I guess GPU was being overridden.

If you changed:
  BUGWK70748 GPU : media/audio-controls-rendering.html = IMAGE
to:
  BUGWK70748 GPU SNOWLEOPARD WIN LINUX : media/audio-controls-rendering.html = IMAGE

I think it would fix your problem since it doesn&apos;t overlap the previous SKIP line.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>500049</commentid>
    <comment_count>10</comment_count>
    <who name="Andrew Scherkus">scherkus</who>
    <bug_when>2011-11-10 10:54:28 -0800</bug_when>
    <thetext>(In reply to comment #9)
&gt; (In reply to comment #8)
&gt; &gt; (In reply to comment #7)
&gt; &gt; &gt; This specific case seems like a bug since the SKIP line refers to GPU and the more specific line refers to CPU.  I wouldn&apos;t expect
&gt; &gt; &gt;   CPU : media/audio-controls-rendering.html = IMAGE
&gt; &gt; &gt; to override
&gt; &gt; &gt;   WONTFIX SKIP GPU GPU-CG LEOPARD : media = PASS TIMEOUT FAIL
&gt; &gt; 
&gt; &gt; Check out the diff:
&gt; &gt; https://trac.webkit.org/changeset/99789/trunk/LayoutTests/platform/chromium/test_expectations.txt
&gt; &gt; 
&gt; &gt; It looks like it was listed as:
&gt; &gt; BUGWK70748 CPU : media/audio-controls-rendering.html = IMAGE 
&gt; &gt; BUGWK70748 GPU : media/audio-controls-rendering.html = IMAGE 
&gt; &gt; 
&gt; &gt; So in this case I guess GPU was being overridden.
&gt; 
&gt; If you changed:
&gt;   BUGWK70748 GPU : media/audio-controls-rendering.html = IMAGE
&gt; to:
&gt;   BUGWK70748 GPU SNOWLEOPARD WIN LINUX : media/audio-controls-rendering.html = IMAGE
&gt; 
&gt; I think it would fix your problem since it doesn&apos;t overlap the previous SKIP line.

With updating test_expectations.txt being a collaborative effort is it reasonable to expect folks to notice situations like this and write fine-grained expectations?

The person who added this expectation would have to be aware that compositing isn&apos;t not enabled on LEOPARD.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>500050</commentid>
    <comment_count>11</comment_count>
    <who name="Ojan Vafai">ojan</who>
    <bug_when>2011-11-10 10:57:08 -0800</bug_when>
    <thetext>(In reply to comment #10)
&gt; With updating test_expectations.txt being a collaborative effort is it reasonable to expect folks to notice situations like this and write fine-grained expectations?
&gt; 
&gt; The person who added this expectation would have to be aware that compositing isn&apos;t not enabled on LEOPARD.

Not at all reasonable IMO. I don&apos;t see a better solution though other than generally reducing the complexity of the test_expectations format. I guess your proposal here to bake it into run-webkit-tests is one solution. That carries the problem of making it harder to know why a test is/isn&apos;t being run because now you need to know both how test_expectations works and what run-webkit-tests hard-codes.

Definitely open to suggestions on how to make this easier to maintain/understand. It&apos;s crazy confusing right now.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>500052</commentid>
    <comment_count>12</comment_count>
    <who name="Andrew Scherkus">scherkus</who>
    <bug_when>2011-11-10 10:59:39 -0800</bug_when>
    <thetext>(In reply to comment #11)
&gt; (In reply to comment #10)
&gt; &gt; With updating test_expectations.txt being a collaborative effort is it reasonable to expect folks to notice situations like this and write fine-grained expectations?
&gt; &gt; 
&gt; &gt; The person who added this expectation would have to be aware that compositing isn&apos;t not enabled on LEOPARD.
&gt; 
&gt; Not at all reasonable IMO. I don&apos;t see a better solution though other than generally reducing the complexity of the test_expectations format. I guess your proposal here to bake it into run-webkit-tests is one solution. That carries the problem of making it harder to know why a test is/isn&apos;t being run because now you need to know both how test_expectations works and what run-webkit-tests hard-codes.
&gt; 
&gt; Definitely open to suggestions on how to make this easier to maintain/understand. It&apos;s crazy confusing right now.

To be clear I&apos;m not 100% thrilled with it either -- it took me a good deal of grepping just to find out how media tests were getting run on GPU bots in the first place!

GPU tests are definitely a little strange as they only run small subset but share the test_expectations.txt file.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>500056</commentid>
    <comment_count>13</comment_count>
    <who name="Tony Chang">tony</who>
    <bug_when>2011-11-10 11:05:41 -0800</bug_when>
    <thetext>From offline discussion with Ojan:

Part of the problem is it&apos;s hard to figure out which lines in test_expectations.txt apply to a specific config.  One solution would be to linkify the expectations on the flakiness dashboard and clicking on it would show you which lines apply to that test on that builder.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>500376</commentid>
    <comment_count>14</comment_count>
    <who name="Dirk Pranke">dpranke</who>
    <bug_when>2011-11-10 16:02:17 -0800</bug_when>
    <thetext>The fact that we are subsetting the list of tests running on the GPU bots inside the chromium_gpu.py code is arguably a misfeature, but it does solve the problem you&apos;ve run into (and may be why I&apos;ve left that in until now rather than just WONTFIX SKIPping all of the directories).

I certainly agree that the test_expectations files are fragile and hard to maintain by hand, but I suspect that any format that supports all of the different uses will be at least as complicated. 

One possible option would be to make any directories marked as SKIP override expected results for specific files inside the directory; I am not aware of any case in practice where we want to skip all but X files in a dir, and if we did, we could support that by requiring the user to explicitly list all of the tests to skip.

We could also build up better tools for explaining what tests run where and what the expectations are. It is actually possible to extract that from NRWT now given the appropriate command line flags, but it&apos;s not easy to do so (using the --print trace* options)

Maybe we need a &quot;webkit-patch print-expectations&quot; command that duplicates what we print with --print trace and iterates over all of the ports or something?</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>500379</commentid>
    <comment_count>15</comment_count>
      <attachid>114443</attachid>
    <who name="Dirk Pranke">dpranke</who>
    <bug_when>2011-11-10 16:03:16 -0800</bug_when>
    <thetext>Comment on attachment 114443
Patch

R+&apos;ing this change; it sounds like it will produce the intended result most easily. Scherkus, it&apos;s up to you if you want to land it or just fall back to expectations-based skipping.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>500387</commentid>
    <comment_count>16</comment_count>
    <who name="Ojan Vafai">ojan</who>
    <bug_when>2011-11-10 16:10:09 -0800</bug_when>
    <thetext>(In reply to comment #14)
&gt; One possible option would be to make any directories marked as SKIP override expected results for specific files inside the directory; I am not aware of any case in practice where we want to skip all but X files in a dir, and if we did, we could support that by requiring the user to explicitly list all of the tests to skip.

This makes sense to me. &quot;SKIP cannot be overridden&quot; seems reasonable. It does further complicate things though. :(</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>500440</commentid>
    <comment_count>17</comment_count>
      <attachid>114443</attachid>
    <who name="Andrew Scherkus">scherkus</who>
    <bug_when>2011-11-10 17:46:11 -0800</bug_when>
    <thetext>Comment on attachment 114443
Patch

Clearing flags on attachment: 114443

Committed r99920: &lt;http://trac.webkit.org/changeset/99920&gt;</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>500441</commentid>
    <comment_count>18</comment_count>
    <who name="Andrew Scherkus">scherkus</who>
    <bug_when>2011-11-10 17:46:16 -0800</bug_when>
    <thetext>All reviewed patches have been landed.  Closing bug.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>500442</commentid>
    <comment_count>19</comment_count>
    <who name="Andrew Scherkus">scherkus</who>
    <bug_when>2011-11-10 17:47:39 -0800</bug_when>
    <thetext>Thanks for the review Dirk!

Do you want me to file follow up bugs for some of the ideas discussed here, or should we agree on a reasonable path forward first?</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>500443</commentid>
    <comment_count>20</comment_count>
    <who name="Tony Chang">tony</who>
    <bug_when>2011-11-10 17:48:40 -0800</bug_when>
    <thetext>We probably want to remove the SKIP line from test_expectations to avoid confusion.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>500445</commentid>
    <comment_count>21</comment_count>
    <who name="Dirk Pranke">dpranke</who>
    <bug_when>2011-11-10 17:53:58 -0800</bug_when>
    <thetext>(In reply to comment #19)
&gt; Thanks for the review Dirk!
&gt; 
&gt; Do you want me to file follow up bugs for some of the ideas discussed here, or should we agree on a reasonable path forward first?

Having a &apos;webkit-patch print-expectations&apos; seems like a good idea; please feel free to file a bug for that.

I&apos;m less certain about the SKIP overrides more-specific-paths, but feel free to file a bug to track better ideas for that.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>500452</commentid>
    <comment_count>22</comment_count>
    <who name="Andrew Scherkus">scherkus</who>
    <bug_when>2011-11-10 18:05:06 -0800</bug_when>
    <thetext>Done:
https://bugs.webkit.org/show_bug.cgi?id=72079
https://bugs.webkit.org/show_bug.cgi?id=72080</thetext>
  </long_desc>
      
          <attachment
              isobsolete="0"
              ispatch="1"
              isprivate="0"
          >
            <attachid>114443</attachid>
            <date>2011-11-09 23:41:46 -0800</date>
            <delta_ts>2011-11-10 17:46:11 -0800</delta_ts>
            <desc>Patch</desc>
            <filename>bug-72001-20111109234144.patch</filename>
            <type>text/plain</type>
            <size>1827</size>
            <attacher name="Andrew Scherkus">scherkus</attacher>
            
              <data encoding="base64">U3VidmVyc2lvbiBSZXZpc2lvbjogOTk4MTcKZGlmZiAtLWdpdCBhL1Rvb2xzL0NoYW5nZUxvZyBi
L1Rvb2xzL0NoYW5nZUxvZwppbmRleCBkNzZjMWVjZGIwYTZlMjk5NmRiOTJjYTEyMWU4MTBjZjYx
ZDM4YmIyLi5hYjMyNjZmYzViNDY2MzAxMzVkN2U2NzA0N2Y1Y2ZmODNmMGI4NDcyIDEwMDY0NAot
LS0gYS9Ub29scy9DaGFuZ2VMb2cKKysrIGIvVG9vbHMvQ2hhbmdlTG9nCkBAIC0xLDMgKzEsMTIg
QEAKKzIwMTEtMTEtMDkgIEFuZHJldyBTY2hlcmt1cyAgPHNjaGVya3VzQGNocm9taXVtLm9yZz4K
KworICAgICAgICBbQ2hyb21pdW1dIG9ubHkgcnVuIG1lZGlhIEdQVSBsYXlvdXQgdGVzdHMgb24g
cGxhdGZvcm1zIHN1cHBvcnRpbmcgYWNjZWxlcmF0ZWQgY29tcG9zaXRpbmcKKyAgICAgICAgaHR0
cHM6Ly9idWdzLndlYmtpdC5vcmcvc2hvd19idWcuY2dpP2lkPTcyMDAxCisKKyAgICAgICAgUmV2
aWV3ZWQgYnkgTk9CT0RZIChPT1BTISkuCisKKyAgICAgICAgKiBTY3JpcHRzL3dlYmtpdHB5L2xh
eW91dF90ZXN0cy9wb3J0L2Nocm9taXVtX2dwdS5weToKKwogMjAxMS0xMS0wOSAgS2V2aW4gT2xs
aXZpZXIgIDxrZXZpbm9AdGhlb2xsaXZpZXJzLmNvbT4KIAogICAgICAgICBbd3hdIFVucmV2aWV3
ZWQgYnVpbGQgZml4LiBVcGRhdGUgcHJvamVjdCBmaWxlcyBhbmQKZGlmZiAtLWdpdCBhL1Rvb2xz
L1NjcmlwdHMvd2Via2l0cHkvbGF5b3V0X3Rlc3RzL3BvcnQvY2hyb21pdW1fZ3B1LnB5IGIvVG9v
bHMvU2NyaXB0cy93ZWJraXRweS9sYXlvdXRfdGVzdHMvcG9ydC9jaHJvbWl1bV9ncHUucHkKaW5k
ZXggZTgwNWU2ODcwMjNmNzZiYzE4YmNmY2JlZTg3ZjgyNzgxMWM5OGJjMi4uNzI5ZTkxYTg4ZWYw
ZjdjMmVkYWRlOTE2OWI0YjhmZTgwMGMxNjIyNCAxMDA2NDQKLS0tIGEvVG9vbHMvU2NyaXB0cy93
ZWJraXRweS9sYXlvdXRfdGVzdHMvcG9ydC9jaHJvbWl1bV9ncHUucHkKKysrIGIvVG9vbHMvU2Ny
aXB0cy93ZWJraXRweS9sYXlvdXRfdGVzdHMvcG9ydC9jaHJvbWl1bV9ncHUucHkKQEAgLTc4LDcg
Kzc4LDE1IEBAIGRlZiBfc2V0X2dwdV9vcHRpb25zKHBvcnQsIGdyYXBoaWNzX3R5cGU9J2dwdScp
OgogCiBkZWYgX3Rlc3RzKHBvcnQsIHBhdGhzKToKICAgICBpZiBub3QgcGF0aHM6Ci0gICAgICAg
IHBhdGhzID0gWydjb21wb3NpdGluZycsICdwbGF0Zm9ybS9jaHJvbWl1bS9jb21wb3NpdGluZycs
ICdtZWRpYScsICdhbmltYXRpb25zLzNkJ10KKyAgICAgICAgcGF0aHMgPSBbJ2NvbXBvc2l0aW5n
JywgJ3BsYXRmb3JtL2Nocm9taXVtL2NvbXBvc2l0aW5nJywgJ2FuaW1hdGlvbnMvM2QnXQorCisg
ICAgICAgIGlmIG5vdCBwb3J0Lm5hbWUoKS5zdGFydHN3aXRoKCdjaHJvbWl1bS1ncHUtbWFjLWxl
b3BhcmQnKToKKyAgICAgICAgICAgICMgT25seSBydW4gdGVzdHMgcmVxdWlyaW5nIGFjY2VsZXJh
dGVkIGNvbXBvc2l0aW5nIG9uIHBsYXRmb3JtcyB0aGF0CisgICAgICAgICAgICAjIHN1cHBvcnQg
aXQuCisgICAgICAgICAgICAjIEZJWE1FOiB3ZSBzaG91bGQgYWRkIHRoZSBhYm92ZSBwYXRocyBo
ZXJlIGFzIHdlbGwgYnV0IGxldCdzIHRlc3QKKyAgICAgICAgICAgICMgdGhlIHdhdGVycyB3aXRo
IG1lZGlhIGZpcnN0LgorICAgICAgICAgICAgcGF0aHMgKz0gWydtZWRpYSddCisKICAgICAgICAg
aWYgbm90IHBvcnQubmFtZSgpLnN0YXJ0c3dpdGgoJ2Nocm9taXVtLWdwdS1jZy1tYWMnKToKICAg
ICAgICAgICAgICMgQ2FudmFzIGlzIG5vdCB5ZXQgYWNjZWxlcmF0ZWQgb24gdGhlIE1hYywgc28g
dGhlcmUncyBubyBwb2ludAogICAgICAgICAgICAgIyBpbiBydW5uaW5nIHRoZSB0ZXN0cyB0aGVy
ZS4K
</data>

          </attachment>
      

    </bug>

</bugzilla>