Closed
Bug 571492
Opened 15 years ago
Closed 15 years ago
check that mv-moz2-linux-ix-slave02 is OK
Categories
(Release Engineering :: General, defect, P2)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: armenzg, Assigned: armenzg)
Details
I have pulled this slave out of the pool since it made 4 builds (Linux mozilla-central build) to fail with the same problem.
This started happening on Jun 11 01:27. The slave, nevertheless, was able to do l10n repackages.
This is the problem we got on the set_basedir step:
bash -c pwd
...
error in ShellCommand._startCommand
Traceback (most recent call last):
File "/tools/buildbot-0.8.0/lib/python2.6/site-packages/buildbot-0.8.0-py2.6.egg/buildbot/slave/commands/base.py", line 400, in start
self._startCommand()
File "/tools/buildbot-0.8.0/lib/python2.6/site-packages/buildbot-0.8.0-py2.6.egg/buildbot/slave/commands/base.py", line 528, in _startCommand
usePTY=self.usePTY)
File "/tools/buildbot-0.8.0/lib/python2.6/site-packages/Twisted-9.0.0-py2.6-linux-i686.egg/twisted/internet/posixbase.py", line 220, in spawnProcess
processProtocol, uid, gid, usePTY)
File "/tools/buildbot-0.8.0/lib/python2.6/site-packages/Twisted-9.0.0-py2.6-linux-i686.egg/twisted/internet/process.py", line 809, in __init__
masterfd, slavefd = pty.openpty()
File "/tools/python-2.6.5/lib/python2.6/pty.py", line 29, in openpty
master_fd, slave_name = _open_terminal()
File "/tools/python-2.6.5/lib/python2.6/pty.py", line 70, in _open_terminal
raise os.error, 'out of pty devices'
OSError: out of pty devices
Assignee | ||
Comment 2•15 years ago
|
||
I have put this slave back into the production pool since it stopped having that problem. I will watch how it behaves before closing.
Assignee | ||
Updated•15 years ago
|
Status: ASSIGNED → RESOLVED
Closed: 15 years ago
Resolution: --- → FIXED
Comment 3•15 years ago
|
||
We've seen this on other slaves too. Somehow the permissions of /dev/ptmx get set so that cltbld can't open a pty.
Updated•11 years ago
|
Product: mozilla.org → Release Engineering
You need to log in
before you can comment on or make changes to this bug.
Description
•