Grid self healing should cleanup temp files left by Selion or browsers.

[sebady]

Grid node self healing should cleanup /tmp files left upon browser, node shutdown.
Some example files in /tmp are directories with uuid names, anonymous webdriver profiles etc.

256ed1f9-8aae-4b07-bf33-06bf1a52786f/
. . .
anonymous4623780548331041862webdriver-profile/
..

[mach6]

I'm not sure I agree that this should be a capability of the SeLion Grid "self healing".. How would it identify a file in /tmp that is left over by Selenium, FFDriver, other grid forked processes from one that is not? This should be the function of a maintenance script/activity which is run out of band.

[sebady]

The self healing is fully aware of when the browsers / tests are running and therefore is the ideal place to cleanup these tmp files that are related to browsers.

[mach6]

Okay, yes it knows when/what browsers are launched, but I don't see it. How do you map to the correct files in /tmp? Are you proposing we monitor /tmp for changes with each browser invocation? Is there an API that tells us which/where the temp profile exists so we can delete it?

[sebady]

You can monitor /tmp but I think a simpler cleanup process is possible. Wait till all tests have finished/stopped and browsers terminated during self healing then remove these directories:

/tmp/anonymous*webdriver-profile

Or simply call:
TemporaryFilesystem.getDefaultTmpFS().deleteTemporaryFiles()

The main disadvantage here is this assume(s) one SeLion node process is running.