PSA: run_remote_tests.sh is finally going away

[Christopher Wiley]

If you don't use run_remote_tests.sh, you can stop reading now.

This script has been deprecated for about a year and is no longer supported by the infrastructure team.  Over the last few days I've swept the code base for references to run_remote_test and the last stragglers should go away this week.  test_that supports the majority of the use cases for run_remote_tests (and much more!).

If you still depend on run_remote_tests.sh, do send me mail.

wiley

[Joseph Sussman]

My typical use case for run_remote_tests.sh looks like this:

(chroot)$ ./run_remote_tests.sh --board=${BOARD} --build --remote=localhost --ssh_port 9222 suite:foo

...the key ingredient being the --build option that tells run_remote_test.sh to use local sources instead of having to rebuild autotest-tests or individual tests therein. It is useful for rapid iteration when writing tests. My question is: what would the new supported workflow be for rapid test development? I got the aforementioned command line from this doc:

http://dev.chromium.org/chromium-os/testing/running-smoke-suite-on-a-vm-image

Thanks!

Joe

--
--
Chromium OS Developers mailing list: chromiu...@chromium.org
View archives, change email options, or unsubscribe:
http://groups.google.com/a/chromium.org/group/chromium-os-dev?hl=en

To unsubscribe from this group and stop receiving emails from it, send an email to chromium-os-d...@chromium.org.

[Chris Sosa]

Check out the doc wiley sent out linking to test_that documentation. The key bit was:

• Running emerge after python-only test changes is no longer necessary. test_that uses autotest_quickmerge to copy your python changes to the sysroot.
  

Since this is true, --build is no longer necessary.

-Sosa