Revert "[autotest] Remove synch_id from database"

This reverts commit eb97ee7fffb4a2ef3155b07f2aa71f04d574b642.
But not quite. We never revert DB migration scripts, especially if
they've been run on any servers. So, this CL adds a new migration (111)
to revert the migration (110) that was already applied to the test
To reland, remove synch_id once again via a new migration.

Reason for revert:
This CL requires lab downtime for push-to-prod because host_scheduler
can not be cleanly restarted across this CL.

To push this CL to lab, one must:
- close the lab.
- migrate DB to the new schema (host_scheduler starts failing)
- push the CL to lab (host_scheduler recovers)
- open the lab.

Now is not the time to do this dance, so reverting with the hope to
reland at a better time.

TEST=test_push host_scheduler can start with tip-of-tree code and with
tip-of-prod after applying both migration 110 and 111.

Change-Id: If2f5428f100af400d498eded9dfb08d6f22aa4dc
Tested-by: Prathmesh Prabhu <>
Reviewed-by: Dan Shi <>
5 files changed
tree: 49512f3b80021f552560e739169ce35355115377
  1. apache/
  2. cli/
  3. client/
  4. contrib/
  5. database/
  6. docs/
  7. frontend/
  8. logs/
  9. packages/
  10. puppylab/
  11. results/
  12. scheduler/
  13. server/
  14. site_utils/
  15. test_suites/
  16. tko/
  17. utils/
  18. .gitignore
  19. .quickmerge_sentinel
  21. COMMIT-QUEUE.ini
  23. global_config.ini
  26. metadata.chromium
  27. moblab_config.ini
  28. PRESUBMIT.cfg
  30. ssp_deploy_config.json

Autotest: Automated integration testing for Android and Chrome OS Devices

Autotest is a framework for fully automated testing. It was originally designed to test the Linux kernel, and expanded by the Chrome OS team to validate complete system images of Chrome OS and Android.

Autotest is composed of a number of modules that will help you to do stand alone tests or setup a fully automated test grid, depending on what you are up to. A non extensive list of functionality is:

  • A body of code to run tests on the device under test. In this setup, test logic executes on the machine being tested, and results are written to files for later collection from a development machine or lab infrastructure.

  • A body of code to run tests against a remote device under test. In this setup, test logic executes on a development machine or piece of lab infrastructure, and the device under test is controlled remotely via SSH/adb/some combination of the above.

  • Developer tools to execute one or more tests. test_that for Chrome OS and test_droid for Android allow developers to run tests against a device connected to their development machine on their desk. These tools are written so that the same test logic that runs in the lab will run at their desk, reducing the number of configurations under which tests are run.

  • Lab infrastructure to automate the running of tests. This infrastructure is capable of managing and running tests against thousands of devices in various lab environments. This includes code for both synchronous and asynchronous scheduling of tests. Tests are run against this hardware daily to validate every build of Chrome OS.

  • Infrastructure to set up miniature replicas of a full lab. A full lab does entail a certain amount of administrative work which isn't appropriate for a work group interested in automated tests against a small set of devices. Since this scale is common during device bringup, a special setup, called Moblab, allows a natural progressing from desk -> mini lab -> full lab.

Run some autotests

See the guides to test_that and test_droid:

test_droid Basic Usage

test_that Basic Usage

Write some autotests

See the best practices guide, existing tests, and comments in the code.

Autotest Best Practices

Grabbing the latest source

git clone

Hacking and submitting patches

See the coding style guide for guidance on submitting patches.

Coding Style