| Summary: | [Win] Buildbot cannot trigger a manual build on Windows | ||
|---|---|---|---|
| Product: | WebKit | Reporter: | Brent Fulgham <bfulgham> |
| Component: | Tools / Tests | Assignee: | Brent Fulgham <bfulgham> |
| Status: | RESOLVED FIXED | ||
| Severity: | Normal | CC: | ahmad.saleem792, don.olmstead, Hironori.Fujii |
| Priority: | P2 | ||
| Version: | 528+ (Nightly build) | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
It looks like this only goes away after a reboot. Maybe the act of shutting down the build slave and restarting it doesn't clean up properly? See also http://trac.buildbot.net/ticket/2385. @Fuji & @Don - Is this applicable for 'win-cairo' bots? Or we can mark this as 'RESOLVED CONFIGURATION CHANGED' since AppleWin is gone now. Think we can resolve this |
Any time we request a manual build on a Windows build or test bot, or when we restart a Windows buildbot and new patches are not waiting in the build queue, we get the following error: starting svn operation /usr/bin/svn update --non-interactive --no-auth-cache --revision 164249 in dir /home/buildbot/slave/win-release-tests/build (timeout 1200 secs) watching logfiles {} argv: ['/usr/bin/svn', 'update', '--non-interactive', '--no-auth-cache', '--revision', '164249'] error in RunProcess._startCommand Traceback (most recent call last): File "/usr/lib/python2.6/site-packages/buildbot_slave-0.8.5-py2.6.egg/buildslave/runprocess.py", line 378, in start self._startCommand() File "/usr/lib/python2.6/site-packages/buildbot_slave-0.8.5-py2.6.egg/buildslave/runprocess.py", line 472, in _startCommand msg += " %s=%s\n" % (name, self.environ[name]) UnicodeDecodeError: 'ascii' codec can't decode byte 0xe2 in position 145: ordinal not in range(128) This does not happen on our Mac or Linux platforms. It seems to be a Windows-specific Python or buildbot bug.