Matthew Treinish fe76e50b61 Add total run time to the runs table
This commit adds calculating the total run time in secs and storing
that in the runs table to the script. This also converts the column
in the runs table to be a float not an int. Normally this would
require a separate migration but since I just pushed this I'm
assuming I'm not going to break existing DBs.
2014-06-14 13:53:31 -04:00
2014-06-12 23:59:00 -04:00
2014-06-12 23:59:00 -04:00
2014-06-12 23:59:00 -04:00
2014-06-12 23:59:00 -04:00
2014-06-12 23:59:00 -04:00
2014-06-12 23:59:00 -04:00
2014-06-12 23:59:00 -04:00
2014-06-12 23:59:00 -04:00
2014-06-12 23:59:00 -04:00
2014-06-12 23:59:00 -04:00

subunit2SQL README

subunit2SQL like it's name implies is a tool used for converting subunit streams to data in a SQL database. The motivation is that for multiple distributed test runs that are generating subunit output it is useful to store the results in a unified repository. This is the motivation for the testrepository project which does a good job for centralizing the results from multiple test runs.

Imagine something like the OpenStack CI system where the same basic test suite is normally run several hundreds of times a day. To provide useful introspection on the data from those runs and to build trends over time the test results need to be stored in a format that allows for easy querying. SQL databases make a lot of sense for doing this.

subunit2SQL uses alembic migrations to setup a DB schema that can then be used by the subunit2sql binary to parse subunit streams and populate the DB. Additional it provides a DB API that can be used to query information from the results stored to build other tooling.

Description
Tooling for converting subunit streams into a SQL DB
Readme 6.1 MiB
Languages
Python 99.4%
Shell 0.5%
Mako 0.1%