Bug 108836 – Windows EWS fails, unable to build ImageDiffCG.cpp

• Component: Tools / Tests
• Status: RESOLVED WONTFIX

[Lucas Forschler]

from: http://queues.webkit.org/results/16378156


Failed to run "['/home/buildbot/WebKit/Tools/Scripts/webkit-patch', '--status-host=queues.webkit.org', '--bot-id=APPLE-EWS-1', 'build-and-test', '--no-clean', '--no-update', '--test', '--non-interactive', '--port=win']" exit_code: 2 cwd: /home/buildbot/WebKit

Running run-webkit-tests
Failed to run "['Tools/Scripts/run-webkit-tests', '--no-new-test-results', '--no-show-results', '--exit-after-n-failures=30']" exit_code: 1

Last 500 characters of output:
ing Pre-Build Event...
3>/usr/bin/bash
3>Project : error PRJ0002 : Error result 1 returned from 'C:\Windows\system32\cmd.exe'.
3>Build log was saved at "file://C:\cygwin\home\buildbot\WebKit\WebKitBuild\Release\obj\DumpRenderTree\BuildLog.htm"
3>DumpRenderTree - 1 error(s), 0 warning(s)
========== Build: 0 succeeded, 3 failed, 2 up-to-date, 0 skipped ==========
Compiling DumpRenderTree failed!
Failed to execute Tools/Scripts/old-run-webkit-tests at Tools/Scripts/run-webkit-tests line 106.

Failed to run "['Tools/Scripts/run-webkit-tests', '--no-new-test-results', '--no-show-results', '--exit-after-n-failures=30']" exit_code: 1
Running build-dumprendertree
Building results into: /home/buildbot/WebKit/WebKitBuild
WEBKITOUTPUTDIR is set to: C:\cygwin\home\buildbot\WebKit\WebKitBuild
WEBKITLIBRARIESDIR is set to: C:\cygwin\home\buildbot\WebKit\WebKitLibraries\win
/home/buildbot/WebKit/Tools/Scripts/pdevenv DumpRenderTree.sln /build Release
Setting environment for using Microsoft Visual Studio 2005 x86 tools.

Microsoft (R) Visual Studio Version 8.0.50727.867.
Copyright (C) Microsoft Corp 1984-2005. All rights reserved.
1>------ Build started: Project: ImageDiff, Configuration: Release Win32 ------
1>Performing Pre-Build Event...
1>/usr/bin/bash
1>XXImageDiffXX 
1>Compiling...
1>####### COMPILING 1 FILES USING AT MOST 8 PARALLEL INSTANCES OF cl.exe ###########
1>ImageDiffCG.cpp
1>..\cg\ImageDiffCG.cpp(37) : fatal error C1083: Cannot open include file: 'wtf/Platform.h': No such file or directory
1>Build log was saved at "file://C:\cygwin\home\buildbot\WebKit\WebKitBuild\Release\obj\ImageDiff\BuildLog.htm"
1>ImageDiff - 1 error(s), 0 warning(s)
2>------ Build started: Project: TestNetscapePlugin, Configuration: Release Win32 ------
2>Performing Pre-Build Event...
2>/usr/bin/bash
2>Project : error PRJ0002 : Error result 1 returned from 'C:\Windows\system32\cmd.exe'.
2>Build log was saved at "file://C:\cygwin\home\buildbot\WebKit\WebKitBuild\Release\obj\TestNetscapePlugin\BuildLog.htm"
2>TestNetscapePlugin - 1 error(s), 0 warning(s)
3>------ Build started: Project: DumpRenderTree, Configuration: Release Win32 ------
3>Performing Pre-Build Event...
3>/usr/bin/bash
3>Project : error PRJ0002 : Error result 1 returned from 'C:\Windows\system32\cmd.exe'.
3>Build log was saved at "file://C:\cygwin\home\buildbot\WebKit\WebKitBuild\Release\obj\DumpRenderTree\BuildLog.htm"
3>DumpRenderTree - 1 error(s), 0 warning(s)
========== Build: 0 succeeded, 3 failed, 2 up-to-date, 0 skipped ==========
Compiling DumpRenderTree failed!
Failed to execute Tools/Scripts/old-run-webkit-tests at Tools/Scripts/run-webkit-tests line 106.

[Lucas Forschler]

This doesn't appear to reproduce on every bot.

[Roger Fong]

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).

[Roger Fong]

Keeping bug open to make sure the problem is fixed.

[Alexey Proskuryakov]

The Windows port is gone, closing.