ToT questions

John Schmitt jschmitt at kealia.com
Fri Mar 28 23:08:53 UTC 2003


I have two machines: luai that hosts QMTest and a test machine named
stor02.  stor02 is supposed to run tests that luai sends it (via
QMTest).  I have several copies of QMTest installed on luai and I copy
my test database around as needed.

The official install is luai:/usr/local and its test database is at
/home/build/nightly.

My play install is at luai:/home/jschmitt and its test database is at
/home/jschmitt/nightly.

I created a target that runs '/usr/bin/python -V' and it works well on
the localtarget.  However, on the remote target (i.e., stor02), I can't
get it to run.  Running ps on stor02 to see what's going on I see this:

[jschmitt at stor02 jschmitt]$ ps -auxf
USER       PID %CPU %MEM   VSZ  RSS TTY      STAT START   TIME COMMAND
[snippage...]
jschmitt  2008  1.0  0.2  7052 5476 ?        S    14:39   0:00      \_
/usr/bin/python2 -O /home/jschmitt/q2/lib/qm/qm/test/qmtest.py -D
home/build/nightly remote

In other words, I don't know why QMTest on stor02 is looking for its
test database from /home/build when it should be coming from
/home/jschmitt.  I launch QMTest on luai from /home/jschmitt/q2 with -D
/home/jschmitt/nightly.  I launched QMTest on laui from /usr/local with
-D /home/build/nightly.

Any thoughts?

To relieve QMTest of the job of launching itself on stor02, I launched
qmtest on stor02 with the 'remote' command, and it gave me this:

[jschmitt at stor02 jschmitt]$ /home/jschmitt/q2/bin/qmtest -D
/home/jschmitt/nightly remote

Traceback (most recent call last):
  File "/home/jschmitt/q2/lib/qm/qm/test/qmtest.py", line 78, in ?
    exit_code = command.Execute()
  File "/lib/qm/qm/test/cmdline.py", line 615, in Execute
  File "/lib/qm/qm/test/cmdline.py", line 1153, in __ExecuteRemote
cPickle.UnpicklingError: invalid load key, '
'.

v-----------------------------------------^^^^
Note the newline in the error message; this is not my bogus wrapping


 -- John

(Please pardon the wrapping - I wanted the pasted text to not wrap)




More information about the qmtest mailing list