Actions
HOWTO monitor the automated tests AKA nightlies » History » Revision 14
« Previous |
Revision 14/38
(diff)
| Next »
Yuri Weinstein, 05/11/2015 10:20 PM
Automated tests AKA nightlies¶
The sepia lab runs automated teuthology tests on a regular basis. They are sometime called the nightlies. The schedule of the nightlies is managed by the QE team:
List of suites and watchers¶
Suite | Watchers |
smoke | Sage, Yuri |
big | Sage, Sam |
powercycle | Yuri |
rados | Sage, Sam |
rbd | Josh |
krbd | Josh, Ilya |
rgw | Yehuda |
fs | Greg, John |
kcephfs | Greg, John, Zheng |
knfs | Greg, John, Zheng |
multimds | Greg, John, Zheng |
samba | Greg, John |
ceph-deploy | Travis, Yuri |
upgrade/client-upgrade | Yuri |
upgrade/dumpling-firefly-x | Yuri |
upgrade/firefly-x | Yuri |
upgrade/giant-x | Yuri |
upgrade/firefly | Yuri |
upgrade/hammer | Yuri |
upgrade/giant | Yuri |
suites scheduled to run on current set of supported branches: firefly, giant, hammer, next and master; master runs are used primarily for development purposes, upgrade tests are not scheduled to run on master.
Tools¶
- https://github.com/jcsp/scrape/blob/master/scrape.py
- command line example:
user@machine:~$ python ~/<scrape_dir>/scrape.py /a/<run_name>
- command line example:
Analyze¶
- sorting out the environmental noise
- create new bugs for errors for which there is no match in the tracker
- add a link to the failed job in pre-existing issues found in the tracker (useful to figure out the frequency and helps with debug when there are multiple outputs / logs)
The ceph-qa mailing list¶
The results of the nightlies are published for analysis on the ceph-qa mailing list. For a given release, the issues that make a job fail in the nightlies need to be backported with a higher priority to reduce the noise.
Updated by Yuri Weinstein almost 9 years ago · 14 revisions