@@ -28,7 +28,7 @@ def get_previous_tag(targetrepodir, version, log):
previousmilestone = None
if version:
if not is_release_version(version):
- return subprocess.check_output(["git", "describe", "--abbrev=0"], cwd=targetrepodir).decode('utf-8').strip()
+ return subprocess.check_output(["git", "tag", "-l", "yocto-*"], cwd=targetrepodir).decode('utf-8').split()[-1]
compareversion, comparemilestone, _ = utils.get_version_from_string(version)
compareversionminor = compareversion[-1]
# After ignoring rc part, if we get a minor to 0 on point release (e.g 4.0.0),
This change only affects master builds. These were being compared with the last tag on the master branch which is currently "uninative-5.0" and clearly not what we want to compare to. The next tag back from that is "yocto-5.1" since the 5.2 and 5.3 releases branched before release/tagging and also isn't correct. Instead, list all the yocoto* tags and pick the last one which should be the most recent numerically. That is currently "yocto-5.3". There should be test results available for these and they don't need to be on the master branch history for the regression report to work correctly. Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> --- scripts/send_qa_email.py | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)