tempest-lib migration script generates incorrect sha1s
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
tempest |
Fix Released
|
High
|
Mauro S M Rodrigues |
Bug Description
The tempest-lib migrate_
This means that the sha1s used in the commit message for the tempest-lib migration commit will not match anything in the tempest git history.
For example from the current git log on tempest-lib one sample entry from a migration git commit message is:
ecaa61e Merge "Fail tempest if 0 tests are run"
However when you look at the commit history in tempest there is no commit matching the sha1 ecaa61e, and the sha1 for the commit matching that commit summary is: c6dac5315e909bf
The script will need to be modified to get the sha1s from the full git log instead of a filtered branch.
tags: | added: low-hanging-fruit |
Changed in tempest: | |
assignee: | nobody → Mauro Sergio Martins Rodrigues (maurosr) |
Changed in tempest: | |
status: | Fix Committed → Fix Released |
Hey Mauro,
Are you still working on this?
if not, can i take it?
Thanks,
Chandan Kumar