Closed Bug 843098 Opened 12 years ago Closed 12 years ago

manifest for v1.0.1 builds after 2013-02-18-07 point incorrectly to v1-train/B2G18

Categories

(Release Engineering :: General, defect)

x86
macOS
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: joduinn, Assigned: rail)

References

Details

Attachments

(1 obsolete file)

v1.0.1 manifests upto and including 2013-02-18-07 correctly point to v1.0.1/b2g18_v1_0_1. v1.0.1 manifests after 2013-02-18-07 INcorrectly point to v1-train/b2g18. Examples: http://ftp.mozilla.org/pub/mozilla.org/b2g/manifests/1.0.1/2013-02-17-23/source_unagi_2013-02-17-23.xml Gaia commit: edaca00b1eb7534120b6255db5d5200fb1d86d65 branch v1.0.1 http://ftp.mozilla.org/pub/mozilla.org/b2g/manifests/1.0.1/2013-02-18-07/source_unagi_2013-02-18-07.xml Gaia commit: edaca00b1eb7534120b6255db5d5200fb1d86d65 branch v1.0.1 http://ftp.mozilla.org/pub/mozilla.org/b2g/manifests/1.0.1/2013-02-18-23/source_unagi_2013-02-18-23.xml Gaia commit: 6916e18d1f72936e892543cf4a104a7d457f78ad branch v1-train http://ftp.mozilla.org/pub/mozilla.org/b2g/manifests/1.0.1/2013-02-19-07/source_unagi_2013-02-19-07.xml Gaia commit: 6916e18d1f72936e892543cf4a104a7d457f78ad branch v1-train http://ftp.mozilla.org/pub/mozilla.org/b2g/manifests/1.0.1/2013-02-19-23/source_unagi_2013-02-19-23.xml Gaia commit: 0b7cfe94ef5931ad4eae89542a99d546d42177a1 branch v1-train
looking in http://ftp.mozilla.org/pub/mozilla.org/b2g/manifests/1.0.1/2013-02-20-07/, I see same is also true for: source_otoro.xml source_otoro_2013-02-20-07.xml source_unagi-eng.xml source_unagi-eng_2013-02-20-07.xml source_unagi.xml source_unagi_2013-02-20-07.xml
Attached patch fix the upload paths (obsolete) — Splinter Review
It turns out that we upload some manifest in the wrong directories.
Attachment #716066 - Flags: review?
Attachment #716066 - Attachment is obsolete: true
Attachment #716066 - Flags: review?
Depends on: 841655
It turnes out that bug 843098 has the fix, which wasn't landed yet. I pushed the change and triggered a nightly build to fix the problem.
Note for myself: check the 23:00 nightly build tomorrow morning.
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
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.

Attachment

General

Created:
Updated:
Size: