At the moment, the names of scripts such as runtestsremote.py are in mozharness: http://mxr.mozilla.org/build/source/mozharness/configs/android/android_panda_releng.py It would make it easier for me to experiment with new test harness code on try if they were in-tree, at: http://mxr.mozilla.org/mozilla-central/source/testing/config/mozharness/android_panda_config.py (The script locations are in-tree for tegras.)
+1 Just to note that because mozharness operates across branches, moving configs in-tree means we either have to: 1) Land the m-c change on every branch that runs in tbpl, or 2) Duplicate the configs in-tree and in mozharness, and have the mozharness script fallback if the in-tree one doesn't exist.
I'm going to use bug 1070041 to tackle this.
Code has landed in bug 1070041 which add run_filename for panda jobs. http://hg.mozilla.org/mozilla-central/file/9bb8b0b4daae/testing/config/mozharness/android_panda_config.py