[Webkit-unassigned] [Bug 50824] When the build is broken on Windows, it isn't clear what project is to blame

[bugzilla-daemon at webkit.org]

https://bugs.webkit.org/show_bug.cgi?id=50824





--- Comment #2 from Adam Roben (aroben) <aroben at apple.com>  2010-12-10 10:44:37 PST ---
(In reply to comment #1)
> Another possible fix (for the bots) would be to have build-webkit build each vcproj individually rather than relying on a sln to build all of them.
> 
> Then we could check the exit code after each build and not kick off the subsequent build when one failed.
> 
> The downside of this approach would be that it is a little more maintenance work since we'd need to keep the project list in build-webkit up-to-date.

That's true, that could make the bot output even clearer. But we could probably achieve the same effect by having build-webkit find the first failing project for you and print it at the end.

Even if we don't do either of those things, I think having output like "JavaScriptCore failed to build. Aborting build of $(ProjectName)." would be pretty clear.

-- 
Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.