UTAH

Merge lp:~xnox/utah/fix-validation-on-release-day into lp:utah

  1. fix-validation-on-release-day
  2. Merge into dev
Proposed by Dimitri John Ledkov
Status: Merged
Approved by: Joshua Powers
Approved revision: 1145
Merged at revision: 1145
Proposed branch: lp:~xnox/utah/fix-validation-on-release-day
Merge into: lp:utah
Diff against target: 13 lines (+1/-2)
1 file modified
utah/isotest/iso_static_validation.py (+1/-2)
To merge this branch: bzr merge lp:~xnox/utah/fix-validation-on-release-day
Reviewer Review Type Date Requested Status
Paride Legovini Pending
Canonical CI Engineering Pending
Review via email: mp+366263@code.launchpad.net

Commit message

We used to know the next codename ahead of time, such that we always knew what the devel series are.

However, not anymore.

In practice, however. When the new codename is not known yet it means that /daily points to stable() still, and we should continue to use "/daily" paths for the stable release whichever it might be, instead of the "/$codename/daily" paths.

This should unbreak testing LTS dailies, when there is no next-devel codename name SRUed in the distro-info-data.

To post a comment you must log in.

Preview Diff

[H/L] Next/Prev Comment, [J/K] Next/Prev File, [N/P] Next/Prev Hunk
1=== modified file 'utah/isotest/iso_static_validation.py'
2--- utah/isotest/iso_static_validation.py 2019-04-17 10:32:51 +0000
3+++ utah/isotest/iso_static_validation.py 2019-04-18 12:08:45 +0000
4@@ -173,8 +173,7 @@
5 try:
6 ubuntu_distro_devel = distro_info.UbuntuDistroInfo().devel()
7 except:
8- self.fail("Can not find distro info details. "
9- "Distro info data could be out of date")
10+ ubuntu_distro_devel = distro_info.UbuntuDistroInfo().stable()
11
12 if self.st_release != ubuntu_distro_devel:
13 self.url = os.path.join(DEFAULT_URL, self.st_release)

Subscribers

People subscribed via source and target branches