It seems likely that this feature is going to rely on parsing the suite name out of the run name - unless we want to modify teuthology to keep track of which suite each job is generated by. I'm not sure we do.
[x] Add Run.suite property
[x] Add Run.ceph_branch or Run.ceph_sha1 property?
[ ] Add Run.machine_type property?
[x] Add some sort of API for "what is the next most recent run of this suite (probably on the same branch and machine_type"
Next step is comparing run results, à la:
$ ./compare.py teuthology-2013-10-22_15:11:33-rgw-next-testing-basic-plana teuthology-2013-10-22_15:11:26-rgw-next-testing-basic-plana
[...]
P => P rgw/multifs/{clusters/fixed-2.yaml fs/ext4.yaml tasks/rgw_s3tests.yaml}
P => P rgw/multifs/{clusters/fixed-2.yaml fs/ext4.yaml tasks/rgw_swift.yaml}
P => F rgw/multifs/{clusters/fixed-2.yaml fs/xfs.yaml tasks/rgw_readwrite.yaml}
[...]
It seems likely that this feature is going to rely on parsing the suite name out of the run name - unless we want to modify teuthology to keep track of which suite each job is generated by. I'm not sure we do.
Run.suitepropertyRun.ceph_branchorRun.ceph_sha1property?Run.machine_typeproperty?Next step is comparing run results, à la:
... But that can be a separate ticket.