| 2d3884ade80ee5a8e2316ddc0996e7a1a12d58da |
|
06-Mar-2017 |
Prathmesh Prabhu <pprabhu@chromium.org> |
Revert "[autotest] Remove synch_id from database"
This reverts commit c744f5fa4992f996768a4857c28fcc8045ea9df1.
Reason for revert: We don't want lab downtime today. We decided
to batch up some outstanding DB changes and do it in one fell
swoop. I'm just the executor...
Original change's description:
> [autotest] Remove synch_id from database
>
> BUG=chromium:687781
> TEST=Run migrate.py sync back and forth
>
> Change-Id: Ieed2052c9aa6958cf3fb6081ee310499c233d112
> Reviewed-on: https://chromium-review.googlesource.com/449972
> Reviewed-by: Allen Li <ayatane@chromium.org>
> Commit-Queue: Allen Li <ayatane@chromium.org>
> Tested-by: Allen Li <ayatane@chromium.org>
>
TBR=pprabhu@chromium.org,xixuan@chromium.org,ayatane@chromium.org
BUG=chromium:687781
BUG=chromium:691084
Change-Id: Ia822a826f8f63dbe32c435adf9e4aea2045a6c3f
Reviewed-on: https://chromium-review.googlesource.com/450837
Reviewed-by: Ningning Xia <nxia@chromium.org>
Reviewed-by: Prathmesh Prabhu <pprabhu@chromium.org>
Commit-Queue: Ningning Xia <nxia@chromium.org>
Tested-by: Ningning Xia <nxia@chromium.org>
/external/autotest/frontend/afe/rdb_model_extensions.py
|
| c744f5fa4992f996768a4857c28fcc8045ea9df1 |
|
11-Feb-2017 |
Allen Li <ayatane@chromium.org> |
[autotest] Remove synch_id from database
BUG=chromium:687781
TEST=Run migrate.py sync back and forth
Change-Id: Ieed2052c9aa6958cf3fb6081ee310499c233d112
Reviewed-on: https://chromium-review.googlesource.com/449972
Reviewed-by: Allen Li <ayatane@chromium.org>
Commit-Queue: Allen Li <ayatane@chromium.org>
Tested-by: Allen Li <ayatane@chromium.org>
/external/autotest/frontend/afe/rdb_model_extensions.py
|
| 076a655d23cfd631b73bb668de46a236c1c16497 |
|
28-Feb-2017 |
Prathmesh Prabhu <pprabhu@chromium.org> |
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
servers.
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.
BUG=chromium:696691
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
Reviewed-on: https://chromium-review.googlesource.com/447200
Tested-by: Prathmesh Prabhu <pprabhu@chromium.org>
Reviewed-by: Dan Shi <dshi@google.com>
/external/autotest/frontend/afe/rdb_model_extensions.py
|
| eb97ee7fffb4a2ef3155b07f2aa71f04d574b642 |
|
11-Feb-2017 |
Allen Li <ayatane@chromium.org> |
[autotest] Remove synch_id from database
BUG=chromium:687781
TEST=Run migrate.py sync back and forth
Change-Id: Ib066b19d90b18ae9926e8aec2c871b963e6a2465
Reviewed-on: https://chromium-review.googlesource.com/441107
Commit-Ready: Allen Li <ayatane@chromium.org>
Tested-by: Allen Li <ayatane@chromium.org>
Reviewed-by: Dan Shi <dshi@google.com>
/external/autotest/frontend/afe/rdb_model_extensions.py
|
| e4c08273f039d97349999818e25fedbb13cdcb4b |
|
02-Feb-2017 |
Allen Li <ayatane@chromium.org> |
[autotest] Remove synch_id concept
BUG=chromium:687781
TEST=None
Change-Id: Ibbef8f7b58d7bb26dcbbe85df308b9e0c4b86bd9
Reviewed-on: https://chromium-review.googlesource.com/435711
Commit-Ready: Allen Li <ayatane@chromium.org>
Tested-by: Allen Li <ayatane@chromium.org>
Reviewed-by: Allen Li <ayatane@chromium.org>
/external/autotest/frontend/afe/rdb_model_extensions.py
|
| 53cc141a0b2ba102f773127184c67dcdf3dce523 |
|
08-Oct-2015 |
MK Ryu <mkryu@google.com> |
[autotest] Make explicit that lock_reason of AbstractHostModel can be NULL.
lock_reason of AbstractHostModel didn't specify null property explicitly.
The effect of it is MySQL has NULL property for lock_reason column, but
Sqlite doesn't have NULL property for the column.
simple_heartbeat_client.py uses in-memory sqlite, and it produces error
like below.
django.db.utils.IntegrityError: NOT NULL constraint failed: afe_hosts.lock_reason
This means a host entry got from prod database has NULL lock_reason,
and it violates integrity for sqlite DB.
We should make it explicit that lock_reason column can be NULL.
BUG=None
TEST=Run simple_heartbeat_client.py in local machine.
Change-Id: Ic2bdb35cff17cf8c1789db78c7166a404610827b
Reviewed-on: https://chromium-review.googlesource.com/304577
Commit-Ready: Mungyung Ryu <mkryu@google.com>
Tested-by: Mungyung Ryu <mkryu@google.com>
Reviewed-by: Matthew Sartori <msartori@chromium.org>
Reviewed-by: Dan Shi <dshi@chromium.org>
/external/autotest/frontend/afe/rdb_model_extensions.py
|
| 6818633834ad52c3de153235639ea9299a6e9a6d |
|
28-Apr-2015 |
Matthew Sartori <msartori@chromium.org> |
[autotest] Require lock reason to lock device
When locking a device, a locking reason now must be provided.
This applies to both adding a new device, and modifying an
existing device from both the web frontend and the atest
command-line tool.
BUG=chromium:336805
DEPLOY=migrate
TEST=Tested adding locked/unlocked devices and locking/unlocking devices
from both the web frontend and using the 'atest host ...' command-line tools.
Change-Id: I3a8cd8891a2999f026dd709ae8a79e2b8cbc251a
Reviewed-on: https://chromium-review.googlesource.com/267595
Tested-by: Matthew Sartori <msartori@chromium.org>
Reviewed-by: Dan Shi <dshi@chromium.org>
Commit-Queue: Matthew Sartori <msartori@chromium.org>
/external/autotest/frontend/afe/rdb_model_extensions.py
|
| 042c1479b8df4f2d87586815d7ad0646cc39abeb |
|
23-Oct-2014 |
Fang Deng <fdeng@chromium.org> |
[autotest] record autoserv run time in metadata db.
Measure autoserv run time and send it to metadata db.
The job id (or special task id) is extracted from the
result directory path using regular expression.
TEST=1)locally run autoserv. 2) Run run_suite.
Made sure that all the special tasks have been excercised.
3) run test_that
BUG=chromium:426105,chromium:422581
Change-Id: I16b119dbcf9b163967abed09a303d86568ea1394
Reviewed-on: https://chromium-review.googlesource.com/225236
Reviewed-by: Fang Deng <fdeng@chromium.org>
Commit-Queue: Fang Deng <fdeng@chromium.org>
Tested-by: Fang Deng <fdeng@chromium.org>
/external/autotest/frontend/afe/rdb_model_extensions.py
|
| 489b91d72cd225e902081dbd3f9e47448fe867f6 |
|
15-Mar-2014 |
Prashanth B <beeps@google.com> |
[autotest] Establish a common interface for host representation.
This cl has the work needed to ensure that schema changes made on
the server trickled down into the client. If the same changes don't
reflect on the client, creating or saving a client host wrapper for
a given host will fail deterministically on the client side until
modules using the rdb_host are modified to reflect the changes.
1. rdb_hosts: A module containing the host heirarchy needed to
establish a dependence between the creation of the RDBServerHostWrapper
(which is serialized and returned to the client, which converts it
into an RDBClientHostWrapper) and the saving of the RDBClientHostWrapper
through and rdb update request.
2. rdb_requests: Contains the requests/request managers that were in
rdb_utils, because I plan to expand them in subsequent cls.
3. rdb_model_extensions: Contains model classes common
to both server and client that help in establishing
the common host model interface.
4. rdb integration tests.
TEST=Ran suites, unittests
BUG=chromium: 348176
DEPLOY=scheduler
Change-Id: I0bbab1dd184e505b1130ee73714e45ceb7bf4189
Reviewed-on: https://chromium-review.googlesource.com/191357
Commit-Queue: Prashanth B <beeps@chromium.org>
Tested-by: Prashanth B <beeps@chromium.org>
Reviewed-by: Dan Shi <dshi@chromium.org>
/external/autotest/frontend/afe/rdb_model_extensions.py
|