On 11/11/2013 02:24 AM, liyang wrote: > Hello chris and other guys, > > I got an headache on one question.
Uhhh, these problems give me a headache also. Though, since you can reproduce it, it will be easier. I would suggest pausing the test after fork_start() somewhere (i.e. with pdb), then go examine all the running processes in proc, pstree, etc. Continue the test, then re-examine the left-over processes. They must be waiting for some condition to occur that will never once the main processes have exited. It could be there's a lock-file race where one set of processes clobbers the other's lock-file (i.e. so they're both watching different lock files with the same name, different inode). Kudo's to you if you can figure it out, these are some of the most tricky problems. The good news is, it's probably not hard to fix once you find the cause :) -- Chris Evich, RHCA, RHCE, RHCDS, RHCSS Quality Assurance Engineer e-mail: cevich + `@' + redhat.com o: 1-888-RED-HAT1 x44214 _______________________________________________ Virt-test-devel mailing list [email protected] https://www.redhat.com/mailman/listinfo/virt-test-devel
