I should also note that: webkit-patch failure-reason
is useful for tracking down when layout test failures started. However it doesn't understand test-webkitpy failures. -eric On Fri, Dec 24, 2010 at 1:52 PM, Eric Seidel <[email protected]> wrote: > More clearly stated: > > The warning about not running the QueueStatusServer tests is a red > herring. Most bots don't run those (because they require having > Google App Engine development kit installed on your machine). > > I've never seen test-webkitpy "complete" like this, and yet buildbot > still think it's running? > > So someone will have to look at the actual Gtk machine. As far as I > can tell, test-webkitpy is functioning normally. > > -eric > > On Fri, Dec 24, 2010 at 1:50 PM, Eric Seidel <[email protected]> wrote: >> The QueueStatusServer tests are optional: >> test-webkitpy: WARNING Skipping tests in ./Tools/QueueStatusServer >> due to failure (No module named dev_appserver). This module is >> optional. The failure is likely due to a missing Google AppEngine >> install. (http://code.google.com/appengine/downloads.html) >> >> It's reaching the end of test-webkitpy: >> Ran 754 tests in 23.696s >> >> OK >> >> But then buildbot seems to think the process never ended and >> eventually times out and kills it: >> >> command timed out: 1200 seconds without output, killing pid 7508 >> process killed by signal 9 >> program finished with exit code -1 >> elapsedTime=1224.572612 >> >> This seems to be a slave-specific issue. >> >> Perhaps whoever runs the Gtk build slave could look at the machine. >> >> -eric >> >> On Fri, Dec 24, 2010 at 1:38 PM, Darin Adler <[email protected]> wrote: >>> Hi folks. >>> >>> The GTK bots have been red for a while now; not sure whether it’s been days >>> or weeks. These are core builders, so should not be red for that long. >>> Apparently the issue is that some Python tests can’t be run because there’s >>> a Google python module of some sort that must be installed. Could someone >>> fix this? Here are possible ways to fix it: >>> >>> 1) Turn off these tests for GTK. >>> 2) Install that module on the bots, if that’s appropriate. >>> 3) Take the GTK bots out of the core set. >>> 4) Undo whatever change made this problem start to occur recently. >>> >>> Anyone? >>> >>> -- Darin >>> >>> _______________________________________________ >>> webkit-dev mailing list >>> [email protected] >>> http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev >>> >> > _______________________________________________ webkit-dev mailing list [email protected] http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev
