Bug #6068
teuthology suite should be able to pick test suites corresponding to the OS-type
90%
Description
currently, teuthology suites runs all tests against all OS type
For example: With the arm testing in progress, we dont need to run fuse tests on the arm setup, as it is not applicable.
we are looking at a solution, that would enable picking suites based on the given os type or linux distribution.
History
#1 Updated by Sandon Van Ness over 10 years ago
So I was talking to Tamil about various ways to go about this. If we are just talking about arm machines in general then I think going by arch (which is already stored in the db which we could figure out from machine_type assuming that all machines of that type are the same arch.
The other option we could do (which I mentioned) is have some sort of exclude string (maybe RE, or make it a list or something) or something that is passed in by schedule_suite.sh that teuthology-suite can look at and not schedule tests if the string matches the description/name of a test or something.
Tamil mentioned going by the os version as they are quantal. We could possibly go that route as well but these are things we would need to add to the yaml and possibly have things hard-coded in schedule_suite.sh for what the distro version is by the machine_type or something.
#2 Updated by Sage Weil over 10 years ago
we could mark the yaml fragments with something like:
exclude_arch: arm*
and any job that comes out with something like that will be skipped/ignored/not scheduled. that way the btrfs.yaml (nested.. wherever) can have that line and it will Do The Right thing..
#3 Updated by Tamilarasi muthamizhan over 10 years ago
- Assignee set to Sandon Van Ness
It would be nice to get the nightlies on the arm setup running soon :)
#4 Updated by Sandon Van Ness over 10 years ago
- Status changed from New to In Progress
- % Done changed from 0 to 80
I got a working solution which is committed but zack had some suggestions for cleaning the code up. I unfortunately did not have time to re-write it today and I am likely not going to be able to work on it at all tomorrow as I will be at the DC so I commited my code for now but have plans to make it more elegant next week.
The fugly commit:
2ea841cdd3f41c829d7874456346893c7c0527cf
And somewhat related (makes sure baremetal does not re-run identical tests as we don't do multi-distro baremetal yet):
dad8d1aa3adf44e4f734cc51faa86d217b7a5e0c
I setup a cron for ceph-deploy tests on arm (saya) in the meantime for master/next.
#5 Updated by Sandon Van Ness over 10 years ago
- Status changed from In Progress to Resolved
- % Done changed from 80 to 100
This has been merged.
#6 Updated by Sandon Van Ness over 10 years ago
- Status changed from Resolved to In Progress
- % Done changed from 100 to 90
Actually this has not. Confused it with the distro kernel one.
#7 Updated by Sandon Van Ness over 10 years ago
- Status changed from In Progress to Resolved
er I was doubly confused. This was merged. For some reason I thought baremetal re-imaging.