<?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>141175</bug_id>
          
          <creation_ts>2015-02-02 14:38:16 -0800</creation_ts>
          <short_desc>[Win] Open Source and EWS bots should present filtered build logs with useful content</short_desc>
          <delta_ts>2015-03-05 09:56:34 -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>Tools / Tests</component>
          <version>528+ (Nightly build)</version>
          <rep_platform>Unspecified</rep_platform>
          <op_sys>Unspecified</op_sys>
          <bug_status>NEW</bug_status>
          <resolution></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="Brent Fulgham">bfulgham</reporter>
          <assigned_to name="Nobody">webkit-unassigned</assigned_to>
          <cc>ap</cc>
    
    <cc>bfulgham</cc>
          

      

      

      

          <comment_sort_order>oldest_to_newest</comment_sort_order>  
          <long_desc isprivate="0" >
    <commentid>1066234</commentid>
    <comment_count>0</comment_count>
    <who name="Brent Fulgham">bfulgham</who>
    <bug_when>2015-02-02 14:38:16 -0800</bug_when>
    <thetext>I have encountered a number of cases recently where build failures encountered by EWS were not able to be diagnosed from the build logs because Visual Studio produces so much output that the relevant error messages were not contained within the first 500 characters of logging.  For example, in &lt;https://webkit-queues.appspot.com/results/5200799210668032&gt; we have an EWS failure that contains a log file with no errors. It simply contains a series of &quot;Build succeeded&quot; messages, followed by a &quot;Build Failed&quot; with no explanation.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>1066310</commentid>
    <comment_count>1</comment_count>
    <who name="Brent Fulgham">bfulgham</who>
    <bug_when>2015-02-02 18:02:20 -0800</bug_when>
    <thetext>Another good example: &lt;https://webkit-queues.appspot.com/results/6313512225734656&gt;. How can anyone tell what&apos;s wrong?</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>1074553</commentid>
    <comment_count>2</comment_count>
    <who name="Brent Fulgham">bfulgham</who>
    <bug_when>2015-03-05 09:56:34 -0800</bug_when>
    <thetext>This problem may be largely resolved by Bug 140845, since we can pass the &quot;/verbosity:minimal&quot; flag to MSBuild.</thetext>
  </long_desc>
      
      

    </bug>

</bugzilla>