754075 - make remote-only tests invalid without remote invocation

Status: RESOLVED WONTFIX

(Testing :: Talos, defect)

Description

[Jeff Hammel]

From https://bugzilla.mozilla.org/show_bug.cgi?id=704654#c65 :

> we might want to fix this in the future so remote only tests are not
  valid without specifying remote options (like ip address and
  webserver)

This is indeed what we want to do.  Tests should probably have a flag,
e.g. remote_only, which is checked for given a remote non-remote run.

Comment 1

[cmtalbert]

This isn't really clear enough to be a mentored bug. BYK can you detail a little more about problem we're trying to solve and what you imagine is required and what you want to see from the contributors that might stop by and work on it.  Also, if you're no longer interested in mentoring this bug then let us know that too.

Comment 2

[Burak Yiğit Kaya [:BYK]]

Sorry for the late response. What is needed here is to not run remote tests unless the necessary "remote" configuration is provided such as the IP address for the remote device.

For this to happen, it looks like first we need a "remote_only" flag to mark a test as, well remote-only, and not run it if we don't have necessary remote configuration.

Comment 3

[Joel Maher ( :jmaher ) (UTC -8)]

moving the remaining android talos tests to autophone this quarter, autophone is more robust in device management and retrying, most likely we will not see this issue there.