[qmtest] "[Errno 3] No such process" problem on Ubuntu

[Stefan Seefeld]

Edisson Braga Jr. wrote:
> Hi,
> 
> We're trying to work with QMTest, but we are getting some problems to have it running on Ubuntu machines.
> 
> The problem we have is similar to the ones reported in http://www.codesourcery.com/archives/qmtest/msg01223.html and http://www.codesourcery.com/archives/qmtest/msg01196.html. In some situations, like running a shell command test on the GUI or just calling "python setup.py check", QMTest returns an exception "[Errno 3] No such process".
> 
> I got this problem on Ubuntu Edgy (6.10), which is the current stable version. I also tried on Ubuntu Feisty (7.04), which is currently in a beta version, but I also got the same problem. 
> 
> I also tried on an older Ubuntu version - Ubuntu Dapper (6.06) -  and it worked fine.
> 
> So, do you guys have some new information about this? There is some way to have it running on the current Ubuntu versions? Since this problem was also seen in other distributions, there is some solution for this problem on the QMTest side?

As this appears to be a bug in either the kernel or the C library, and I don't see it on my current
system (FC6), I haven't put any efford in working around the problem. May be reporting the bug to
some ubuntu tracker will speed up any relevant upgrade ?


> 
> BTW, I followed the workaround suggested by Stefan in a previous e-mail (catch and ignore that particular exception thrown by os.setpgid() ) and I didn't get the "[Errno 3] No such process" anymore. However, when I run "python setup.py check" sometimes the test freezes at the beginning of the tests during the execution of "xmldb.signals_unblocked". When it doesn't freeze on this point, it will freeze during the SSH test. If I interrupt the execution at this point, the Traceback will show this:
> 
> qmtest: Interrupted.
> Traceback (most recent call last):
>   File "/home/edisson/src/qmsrc/qm-svn/build/scripts-2.4/qmtest", line 132, in ?
>     exit_code = main()
>   File "/home/edisson/src/qmsrc/qm-svn/build/scripts-2.4/qmtest", line 110, in main
>     exit_code = command.Execute()
>   File "/home/edisson/src/qmsrc/qm-svn/build/lib.linux-i686-2.4/qm/test/cmdline.py", line 784, in Execute
>     return method()
>   File "/home/edisson/src/qmsrc/qm-svn/build/lib.linux-i686-2.4/qm/test/cmdline.py", line 1691, in __ExecuteRun
>     if engine.Run():
>   File "/home/edisson/src/qmsrc/qm-svn/build/lib.linux-i686-2.4/qm/test/execution_engine.py", line 275, in Run
>     self._RunTests()
>   File "/home/edisson/src/qmsrc/qm-svn/build/lib.linux-i686-2.4/qm/test/execution_engine.py", line 375, in _RunTests
>     self.__CheckForResponse(wait=1)
>   File "/home/edisson/src/qmsrc/qm-svn/build/lib.linux-i686-2.4/qm/test/execution_engine.py", line 760, in __CheckForResponse
>     fds = select.select (fds, [], [], 0.1)[0]
> KeyboardInterrupt
> interrupted
> 
> I'm using python2.4.
> 
> I would appreciate to have some help on this subject!

Are you expecting to actually use the QMTest GUI (as opposed to the command line interface),
with the ProcessTarget / SSH ? If not I would suggest to simply avoid that particular test
suite (for example by just running 'python setup.py check --serial').

Thanks,
		Stefan

-- 
Stefan Seefeld
CodeSourcery
stefan at codesourcery.com
(650) 331-3385 x718