Bug 141175

Summary: [Win] Open Source and EWS bots should present filtered build logs with useful content
Product: WebKit Reporter: Brent Fulgham <bfulgham>
Component: Tools / TestsAssignee: Nobody <webkit-unassigned>
Status: NEW ---    
Severity: Normal CC: ap, bfulgham
Priority: P2    
Version: 528+ (Nightly build)   
Hardware: Unspecified   
OS: Unspecified   

Description Brent Fulgham 2015-02-02 14:38:16 PST 
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 <https://webkit-queues.appspot.com/results/5200799210668032> we have an EWS failure that contains a log file with no errors. It simply contains a series of "Build succeeded" messages, followed by a "Build Failed" with no explanation.
Comment 1 Brent Fulgham 2015-02-02 18:02:20 PST 
Another good example: <https://webkit-queues.appspot.com/results/6313512225734656>. How can anyone tell what's wrong?
Comment 2 Brent Fulgham 2015-03-05 09:56:34 PST 
This problem may be largely resolved by Bug 140845, since we can pass the "/verbosity:minimal" flag to MSBuild.