Project

General

Profile

Bug #18818

All jobs scheduled using --sha1 show up "branch: master", even if they are {hammer,jewel,kraken}

Added by Nathan Cutler about 6 years ago.

Status:
New
Priority:
Normal
Assignee:
Category:
-
Target version:
-
% Done:

0%

Source:
Tags:
Backport:
Regression:
No
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
Crash signature (v1):
Crash signature (v2):

Description

When a user schedules a run using --ceph $BRANCH, the branch name shows up in the name of the run. Developers are used to parsing the name of the run to see which branch is being tested.

This works fine as long as the runs are scheduled in this way.

If a run is scheduled with --sha1 $SHA1, teuthology uses the default for the branch, which is master. Since master contains all valid SHA1s, it could be argued that this is reasonable. However, since the SHA1/tag does not show up in the run name, it can be confusing.

For example, if I want to test v10.2.4 for some reason, I find the SHA1 corresponding to that tag and do:

teuthology-suite --sha1 $SHA1_CORRESPONDING_TO_V10.2.4_TAG

From the name, the resulting run claims to be "master", but in reality it is jewel.

This could be fixed by having teuthology parse "git describe" to determine the major version and set the value of branch accordingly.

Also available in: Atom PDF