Bug 136950 – Fix the build on the WinCairo buildbot

• Component: New Bugs
• Status: RESOLVED FIXED

[Csaba Osztrogonác]

The build fails on the WinCairo buildbot with the following error:
Building results into: /cygdrive/c/Projects/BuildSlave/win-cairo-release/build/WebKitBuild
WEBKIT_OUTPUTDIR is set to: C:\Projects\BuildSlave\win-cairo-release\build\WebKitBuild
WEBKIT_LIBRARIES is set to: C:\Projects\BuildSlave\win-cairo-release\build\WebKitLibraries\win
/cygdrive/c/Program Files (x86)/Microsoft Visual Studio 12.0/Common7/IDE/WDExpress.exe WebKit.vcxproj\WebKit.sln /build Release_WinCairo|Win32
Could not open build log file at /cygdrive/c/Projects/BuildSlave/win-cairo-release/build/WebKitBuild/Release_WinCairo/BuildOutput.htm at ./Tools/Scripts/build-webkit line 283.
program finished with exit code 2

The error is constant since the resurrection of the bot at 11st Sep (r173534)
(Before it "Failed svn" was the normal on this bot since 27th June - r170535
And before it failed compile-webkit and failed-svn changed periodically ...
The latest success build was on 16th June - r170019.)

So there wasn't any success build on this bot since 3 months. Is it still maintained by anybody?

[Csaba Osztrogonác]

The build is still broken with the same error. Is there any plan to 
fix it, or can we say that the WinCairo buildbot is unmaintained?

[Csaba Osztrogonác]

The WinCairo bot is still broken since 4 months.

Is there any plan to fix and maintain it, or should we simply remove it 
from https://build.webkit.org/waterfall if nobody is interested in it?

(In reply to comment #2)
> The WinCairo bot is still broken since 4 months.
> 
> Is there any plan to fix and maintain it, or should we simply remove it 
> from https://build.webkit.org/waterfall if nobody is interested in it?

Hopefully, it can be fixed by somebody :)

The last build seems to have failed because of a timeout after 1200 seconds, maybe 1200 seconds isn't enough for a complete build?

[Csaba Osztrogonác]

(In reply to comment #3)
> Hopefully, it can be fixed by somebody :)

By the non-existing maintainer, who hasn't been interested in this bot since 4 months? :))

(In reply to comment #4)
> The last build seems to have failed because of a timeout after 1200 seconds, maybe 1200 seconds isn't enough for a complete build?

During a whole month? I don't think so.

[Csaba Osztrogonác]

It seems the build was fixed by the invisible maintainer:
https://build.webkit.org/builders/WinCairo%20Release/builds/43276

Now "only" JSC tests run in an infinite loop.

[Csaba Osztrogonác]

(In reply to comment #6)
> It seems the build was fixed by the invisible maintainer:
> https://build.webkit.org/builders/WinCairo%20Release/builds/43276
> 
> Now "only" JSC tests run in an infinite loop.

As far as I know JSC stress tests doesn't work at all on Windows,
maybe you should disable stress tests similar to Apple Windows port
and run only the old stye mozilla tests:
https://trac.webkit.org/browser/trunk/Tools/Scripts/run-javascriptcore-tests?rev=174096&order=name#L86

(In reply to comment #7)
> (In reply to comment #6)
> > It seems the build was fixed by the invisible maintainer:
> > https://build.webkit.org/builders/WinCairo%20Release/builds/43276
> > 
> > Now "only" JSC tests run in an infinite loop.
> 
> As far as I know JSC stress tests doesn't work at all on Windows,
> maybe you should disable stress tests similar to Apple Windows port
> and run only the old stye mozilla tests:
> https://trac.webkit.org/browser/trunk/Tools/Scripts/run-javascriptcore-tests?rev=174096&order=name#L86

The stress tests are working on Windows, although there are some failures (18).
I think it would be nice to have them running on the WinCairo bot :)

[Csaba Osztrogonác]

(In reply to comment #6)
> It seems the build was fixed by the invisible maintainer:
> https://build.webkit.org/builders/WinCairo%20Release/builds/43276
> 
> Now "only" JSC tests run in an infinite loop.

And after the first success build + infinite loop JSC test, 
the bot is dead again 4.5 days ago.