Actions
Feature #8363
closedCreate a long-ish running teuthology job for teuthology testing
Status:
Closed
Priority:
Normal
Assignee:
-
Category:
-
% Done:
0%
Source:
other
Tags:
Backport:
Reviewed:
Affected Versions:
Description
We should create one or up to a few yaml files to use as jobs for testing teuthology. They should use a known-good version of ceph, and exercise as many tasks as is reasonable. The quick-running tasks should run before the longer-running ones.
Updated by Zack Cerza almost 10 years ago
My current thought is:
- For each suite that was run in the last week:
- Select, say, the most recent run on the master (or firefly) branch
- Select the shortest-running job in that run
- Take a copy of the
orig.config.yamlfor the job, and generalize it by removing anything specific to that particular instance
- Use the selected generalized job configurations to generate a single one, using two or three machines to preserve resources
Updated by Zack Cerza over 9 years ago
- Status changed from New to Closed
This effectively is done by upgrade tests
Actions