On 11/01/13 09:48, Scott Kostyshak wrote:
>
> I guess we should wait for Tommaso.
FYI [1].
Perhaps, if you're playing with these tests, you may have needed to stop them
via the GUI button. Now, that doesn't really work too well, and often we have
stale lyx processes / .sh/python scripts running in the background that keep
spawning further LyX instances, etc.... under such conditions, running further
tests starts failing miserably. A "ps aux | grep lyx" normally catches such
stale processes, if any. A run of "killall lyx python sh bash" (not as root!)
might help in such regard, but beware that you can kill other possibly useful
stuff that's running on the system (e.g., applets in the topbar?)
Any fix to the proper action to run when hitting that button is very welcome.
T.
[1]
tommaso@mobiletom:~/lyx-trunk-ws/lyx/development/autotests$ ./run-tests.sh
findadv-*.txt
Running test cases . . .
findadv-01-in.txt: Ok
findadv-02-in.txt: Ok
findadv-03-in.txt: Ok
findadv-04-in.txt: Ok
findadv-05-in.txt: Ok
findadv-06-in.txt: Ok
findadv-07-in.txt: Ok
findadv-08-in.txt: Ok
findadv-09-in.txt: Ok
findadv-10-in.txt: Ok
findadv-11-in.txt: Ok
findadv-12-in.txt: Ok
findadv-13-in.txt: Ok
findadv-14-in.txt: Ok
findadv-15-in.txt: Ok
findadv-16-in.txt: Ok
findadv-17-in.txt: Ok
findadv-18-in.txt: Ok
findadv-19-in.txt: Ok
findadv-20-in.txt: Ok
findadv-re-01-in.txt: Ok
findadv-re-02-in.txt: Ok
findadv-re-03-in.txt: Ok
findadv-re-04-in.txt: Ok
All tests SUCCESSFUL
