- 7f0c183 [autotest] Setup chromeos_lab_servers database by Dan Shi · 10 years ago
- 4753990 [autotest] fall back on sqlite3 if pysqlite2 doesn't import by Aviv Keshet · 11 years ago
- 74a314b Upstream Autotest merge. by Dale Curtis · 13 years ago
- fe6f1a4 Add option to database_connection so that logging can be turned on via object creation. by mbligh · 15 years ago
- b21b8c8 Fix handling of database reconnects in the scheduler by enhancing the "django" database_connection backend and having the scheduler use it. This eliminates the duplicate connection that the scheduler was setting up -- now it uses only a single connection (the Django one). by showard · 15 years ago
- 34ab099 beginnings of a new scheduler functional test. this aims to test the entire monitor_db.py file holistically, made possible by the fact that monitor_db.py is already isolated from all direct system access through drone_manager (this was a necessary separation for distributed scheduling). by mocking out the entire drone_manager, as well as other major dependencies (email manager, global config), and filling a test database, we can allow the dispatcher to execute normally and allow it to interact with all the other code in monitor_db. at the end, we can check the state of the database and the drone_manager, and (probably most importantly, given the usual failure mode of the scheduler) we can ensure no exceptions get raised from monitor_db. by showard · 15 years ago
- 89f84db by showard · 16 years ago
- a9a9101 Remove some dead code that was apparently left in database_connection.py. by showard · 16 years ago
- b1e5187 Get the scheduler unittest to run against SQLite! by showard · 16 years ago
- 0e73c85 Add a generic database wrapper, supporting different database backends, to be used by migrate, scheduler, parser (eventually), and maybe others. This will consolidate the multiple database wrappers we have throughout the code and allow us to swap in SQLite for MySQL for unit testing purposes. by showard · 16 years ago