Instruments Trace Complete about appium HOT 10 CLOSED

If appium closes instruments successfully, it will delete the .trace directories by default. If instruments crashes, they won't be deleted. Alternatives are:

• have appium delete extraneous directories on startup too
• create a "grunt cleanup" command that makes it easy to clean things up

from appium.

It'd be nice if they were deleted on startup and when @driver.quit is called.

from appium.

They are deleted in every case that appium itself doesn't crash due to an error or we can't get the name of the tracedir for some reason. So when you call @driver.quit, appium shuts down instruments and retrieves the name of the tracedir which instruments created (which we can always get except maybe in some rare instruments crash cases). It then (by default) removes this tracedir. So if you run a clean test, you should see no tracedirs in your appium directory afterward. Is this not your experience?

If what you're asking about is "how do we get rid of these even when something goes wrong and we can't know that a tracedir was created", then we'll have to resort to some kind of rm -rf *.trace that just gets called at some point in the flow---and even this won't be guaranteed to run if we crash beforehand.

I'm more inclined to (a) try to figure out why these crashes are happening and exit gracefully instead, perhaps removing tracedirs that we detect in another way and (b) adding a "cleanup" script which gets rid of these along with the instruments socket and any other tempfiles that appium might have created. This could be run with grunt clean or something similar.

from appium.

So if you run a clean test, you should see no tracedirs in your appium directory afterward. Is this not your experience?

Appium frequently crashes and I'm left with tons of instrumentscli0.trace folders. I'd rather not have to manually run a cleanup script. Couldn't @driver.quit remove all .trace folders instead of just the most recent one? I don't see why it'd be helpful to retain them.

from appium.

It could, but for some people those tracedirs contain valuable diagnostic information (or so I have been told). I'm fine blowing them all away if a flag is set, though. Another issue with this particular suggestion is that if Appium itself crashes, we can't do anything at all on @driver.quit, since the server is no longer even listening. We could also do it on server startup, which doesn't guarantee no tracedirs ever, but at least keeps things more clean. Anyway, I'll go ahead and implement something that will delete these dirs more often.

from appium.

I guess the real solution is fixing the crash issues then it won't be a problem. A flag would be nice.

execute_script 'mobile: setRemoveAllTraceOnQuit', 1

from appium.

The flag I'm thinking of already exists, it's --remove and on by default when starting the appium server itself (I think this is something for the server to know about, not the client---the client could be on a completely different machine, after all).

from appium.

Sounds good.

from appium.

let me know if this doesn't delete things often enough for you.

from appium.

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

from appium.