Now all pobot processes are killed after test execution

[aaltat]

Now all pobot processes are killed after test execution

[mkorpela]

Thanks for the bug report!

I'm not yet able to reproduce the problem - have to try it again tomorrow!

[mkorpela]

Couldn't reproduce on OS X with chromedriver 2.14, selenium2library 1.6.0.

[mkorpela]

Seems that the hanging process in your case is PabotLib process. Are you using the --pabotlib option?

[aaltat]

Yes I am.

I was thinking that could it be windows is related problem?

[aaltat]

Windows is -> windows OS, dam that auto correction

[aaltat]

Did more investigations, one does not need a Selenium2Library to reproduce the problem. It is enough to call pabot and some BuildIn library keywords to get the pabot process hanging around after the test execution. I use this command:

pabot --pabotlib --resourcefile suites\valueset.dat suites\pabot_fail

And the example suite can be found from here: https://www.dropbox.com/s/kc8uxvg2ym7o30t/suites_v2.zip?dl=0

Seems lot like windows OS problem, because when I run the same suite in my Fedora box, all the pabot process do die nicely when execution is stopped.

[mkorpela]

thanks for debugging! My virtual box windows images aren't currently working. But I'll try to find a working image.

[mkorpela]

Could reproduce the problem in Win 7. Thanks for the report.

[mkorpela]

From the robotremoteserver docs: "Sending the process SIGINT, SIGTERM, or SIGHUP signal. Does not work on Windows. Notice that with Jython you need to send the signal to the started Java process, not to the shell typically started by jython command."
Seems like a new major pabot version is going to be born.

[mkorpela]

Released in 0.12.

[aaltat]

Cool, thanks from help.

[mkorpela]

Do you want the Run only once keyword too?

[aaltat]

Sure, that would be nice.

I did have not so elegant solution in my mind. Call pybot first to only do the run once setup and then call pabot to run the parallel test and combine the result rebot. But implementing the Run Only Once keyword would definitely ease the complexity.

My need is only in the setup. In practise I need create unique users for each parallel test and because I wipe database before test run, I cannot allow each parallel run to use the admin user of the application. The application under test does not cope if same user does many things parallel.