Closed Bug 727740 Opened 13 years ago Closed 13 years ago

release-sanity assumes that in-tree mozconfigs are defined in the release config

Categories

(Release Engineering :: General, defect, P2)

Product:
Release Engineering
Component:
General
Platform:
x86
All
Type:
defect

Tracking

(Not tracked)

Status:
RESOLVED WONTFIX

People

(Reporter: nthomas, Assigned: catlee)

References

Details

(Whiteboard: [release][automation][simple])

Fallout from bug 697611. When starting the 3.6.27 release: (build1)[cltbld@buildbot-master08 master]$ PYTHONPATH=. python ../tools/buildbot-helpers/release_sanity.py -u nthomas -p firefox -V 3.6.27 --branch mozilla-1.9.2 --build-number 1 -c release-firefox-mozilla-1.9.2.py --dryrun localhost:9001 Traceback (most recent call last): File "../tools/buildbot-helpers/release_sanity.py", line 378, in <module> releaseConfig['mozconfigs'], KeyError: 'mozconfigs' We use the mozconfigs in buildbot-configs for 1.9.2.
Component: Release Engineering → Release Engineering: Automation
QA Contact: release → catlee
Whiteboard: [release][automation] → [release][automation][simple]
Priority: -- → P2
Assignee: nobody → catlee
WONTFIX based on the fact this only affects 1.9.2 builds, and we're not expecting to do any more of those. It's also easily worked around by running release_sanity with "--bypass-mozconfig-check"
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → WONTFIX
Product: mozilla.org → Release Engineering
Component: General Automation → General
You need to log in before you can comment on or make changes to this bug.