buildJSCTool was to determine if the run-javascriptcore-tests and run-webkit-tests should build JSC/DRT/WTR or not. These scripts call build-jsc / build-dumprendertree if --no-build isn't passed. Let's see run-javascriptore-tests first. Now master.cfg passes --no-build for all bots, except EFL/GTK "build and tester" bots, where calling build-jsc is unnecessary, because JSC is already built by build-webkit previously. Let's see run-webkit-tests. buildJSCTool is true on non Windows bots and --no-build is explicitly passed to Mac and Win bots unconditionally, but not for EFL/GTK bots when build-dumprendertree/build-webkittestrunner don't do anything useful on EFL and GTK, just simple return 0. So let's remove this huge and misleading cruft and pass --no-build everywhere unconditionally.
Created attachment 246445 [details] Patch
Comment on attachment 246445 [details] Patch Clearing flags on attachment: 246445 Committed r180039: <http://trac.webkit.org/changeset/180039>
All reviewed patches have been landed. Closing bug.
Ryosuke or Lucas, could you apply this change on the master if you have a little bit of free time? Thanks.
done
(In reply to comment #5) > done yay, the bots already picked it up and they are a little bit faster now. :)