At the Community Lab, some developers have noticed an "annoyance" like this:

User 1 with name User1 runs DTS, and it copies a DPDK tarball over to
/tmp/dpdk.tar.xz on the SUT system. It is extracted and owned by user 1. The
testrun completes without issue. 

Later, User 2 tries to run DTS with a DPDK tarball of the same name. In doing
so, the framework tries to delete the previously existing /tmp/dpdk.tar.xz, and
fails as it is running from user User2. 

This behavior was also noted today in copying dpdk-devbind.py to the tester
(/tmp/dpdk-devbind.py cannot be removed by all users). 

So, then the user has to SSH onto the SUT system, and delete the artifact with
sudo.

Some simple solutions are like: 
1. chmod the copied artifacts to allow for all users to delete them.
2. Delete the artifacts as a test run cleanup step.
3. copy all artifacts to something like /tmp/($my_user)/ instead of /tmp/

Or maybe there are some other ideas which are better... feedback is welcome.