- 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
- 6631273 Make a bunch of stuff executable by mbligh · 15 years ago
- 7c8ea99 Not all distros put a symlink in for the python version. However by mbligh · 15 years ago
- 049b0fd add a debug mode to migrations. this is pretty handy for debugging complex migrations. by showard · 15 years ago
- eca1f21 Make migration manager support migration modules with just strings "UP_SQL" and/or "DOWN_SQL". It seems to be a very common case that we just write SQL strings for up and down and then have some boilerplate migrate_up() and migrate_down() methods. Now we won't need those methods in that case. Of course, if you include those methods, they'll still get called instead. by showard · 15 years ago
- b82b1f2 Make a couple of errant files executable by mbligh · 15 years ago
- 89f84db by showard · 15 years ago
- 8bcd23a Move all MySQLdb imports after the 'import common' so that a MySQLdb by mbligh · 15 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
- 0a4e022 Remove unused imports. by showard · 16 years ago
- 442e71e Move migration system into database/ directory. 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