Closed
Bug 697611
Opened 13 years ago
Closed 13 years ago
release_sanity.py should check in-tree mozconfigs if they exist
Categories
(Release Engineering :: General, defect, P3)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: nthomas, Assigned: bhearsum)
References
Details
Attachments
(2 files)
(deleted),
patch
|
lsblakk
:
review+
bhearsum
:
checked-in+
|
Details | Diff | Splinter Review |
(deleted),
patch
|
rail
:
review+
bhearsum
:
checked-in+
|
Details | Diff | Splinter Review |
Right now we don't use in-tree mozconfigs for release builds, but once we merge from central to aurora and beta for Firefox 10 we'll be able to. Probably bug 558180 is where that will happen (*sets dependency*).
release_sanity will then need to learn to look at the in-tree mozconfigs to do the comparisons. This is a followup to bug 386338 (*sets blocking*).
Updated•13 years ago
|
Comment 1•13 years ago
|
||
taking this and changed it to depending on bug 386338 since we needed release_sanity to check mozconfigs at all before we can ask it to check for in-tree or not (as that will be for some branches and not all like mozilla-1.9.2)
Assignee: nobody → lsblakk
Status: NEW → ASSIGNED
Assignee | ||
Comment 3•13 years ago
|
||
This caused an error in the 10.0esr release because we don't have buildbot-configs versions of the mozconfigs at all. Any ETA on this?
Assignee | ||
Comment 4•13 years ago
|
||
Testing out this fix in staging:
diff --git a/buildbot-helpers/release_sanity.py b/buildbot-helpers/release_sanity.py
index 300094b..f40eced 100644
--- a/buildbot-helpers/release_sanity.py
+++ b/buildbot-helpers/release_sanity.py
@@ -110,7 +110,7 @@ def verify_mozconfigs(branch, version, hghost, product, platforms, whitelist=Non
urls = []
mozconfigs = []
for type in types.values():
- urls.append(make_hg_url(hghost, 'build/buildbot-configs', 'http',
+ urls.append(make_hg_url(hghost, branch, 'http',
tag, os.path.join('mozilla2', platform,
branch, type,'mozconfig')))
for url in urls:
Assignee | ||
Comment 5•13 years ago
|
||
I'm working on a fix for this as part of bug 717106, which suffers from this more acutely.
Assignee: lsblakk → bhearsum
Assignee | ||
Comment 6•13 years ago
|
||
This affects ESR more than other branches, because we don't have a full set of mozconfigs in buildbot-configs. Because of that, I had to find a fix.
Attachment #593287 -
Flags: review?(lsblakk)
Comment 7•13 years ago
|
||
Comment on attachment 593287 [details] [diff] [review]
use mozconfigs from release config to find in-repo ones to compare
lgtm, thanks for picking this up
Attachment #593287 -
Flags: review?(lsblakk) → review+
Assignee | ||
Updated•13 years ago
|
Attachment #593287 -
Flags: checked-in+
Assignee | ||
Updated•13 years ago
|
Status: ASSIGNED → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
Comment 8•13 years ago
|
||
Fennec is a good citizen as well :)
PYTHONPATH=. python ../tools/buildbot-helpers/release_sanity.py -u rail -pfirefox,fennec -V 10.0b1 --branch mozilla-beta --build-number 1 -c release-firefox-mozilla-beta.py -c release-fennec-mozilla-beta.py --dryrun localhost:9001 2>&1 | tee rail.out
(build1)[cltbld@buildbot-master08 master]$ PYTHONPATH=. python ../tools/buildbot-helpers/release_sanity.py -u rail -pfirefox,fennec \
> -V 11.0b1 --branch mozilla-beta --build-number 1 -c release-firefox-mozilla-beta.py -c release-fennec-mozilla-beta.py \
> --dryrun localhost:9001 2>&1 | tee rail.out
Traceback (most recent call last):
File "../tools/buildbot-helpers/release_sanity.py", line 365, in <module>
releaseConfig['sourceRepositories']['mozilla']['path'],
KeyError: 'mozilla'
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Assignee | ||
Comment 9•13 years ago
|
||
Attachment #594206 -
Flags: review?(rail)
Updated•13 years ago
|
Attachment #594206 -
Flags: review?(rail) → review+
Assignee | ||
Updated•13 years ago
|
Attachment #594206 -
Flags: checked-in+
Assignee | ||
Updated•13 years ago
|
Status: REOPENED → RESOLVED
Closed: 13 years ago → 13 years ago
Resolution: --- → FIXED
Updated•11 years ago
|
Product: mozilla.org → Release Engineering
You need to log in
before you can comment on or make changes to this bug.
Description
•