Summary: | Windows EWS fails, unable to build ImageDiffCG.cpp | ||
---|---|---|---|
Product: | WebKit | Reporter: | Lucas Forschler <lforschler> |
Component: | Tools / Tests | Assignee: | Nobody <webkit-unassigned> |
Status: | RESOLVED WONTFIX | ||
Severity: | Normal | CC: | ap, jonlee, lforschler, roger_fong |
Priority: | P2 | ||
Version: | 528+ (Nightly build) | ||
Hardware: | Unspecified | ||
OS: | Unspecified |
Description
Lucas Forschler
2013-02-04 09:54:39 PST
This doesn't appear to reproduce on every bot. I've seen this happen locally before. The problem is that if one project happens to fail to build a buildfailed file is created in the build directory. If this buildfailed file persists across builds it affects the next builds results as well. A clean build or just removing the buildfailed file will fix it. I manually got rid of it on ews-1. I checked the other bots just in case and the buildfailed file was not there on those machines (which supports my theory). The buildfailed system is in place so that if one of the 30 some projects in the windows solution fails to build, all the remaining projects will automatically fail to build in the prebuild step as well, instead of still trying and wasting time. While this is usually convenient it also leads to stupid problems like this. The first thing that comes to mind in dealing with the issue long term is to just have a post solution build project that gets rid of the buildfailed file (seems a little heavy weight for something so trivial though). Keeping bug open to make sure the problem is fixed. The Windows port is gone, closing. |