Closed
Bug 628390
Opened 14 years ago
Closed 14 years ago
post_upload.py failed for uploading a locale
Categories
(Release Engineering :: General, defect)
Tracking
(Not tracked)
RESOLVED
DUPLICATE
of bug 613970
People
(Reporter: armenzg, Unassigned)
References
Details
Attachments
(1 file)
3.19 KB,
text/plain
|
Details |
When doing the 3.6.14 release the 'ko' locale failed on "make upload" because post_upload.py failed to find the xpi on /tmp/tmp.PwvADA1541/mac/xpi/ko.xpi Besides the point that it failed I think that we could do something to improve recovery. If a locale fails could we resubmitted as a standalone_repack? Traceback (most recent call last): File "/usr/local/bin/post_upload.py", line 415, in ? func(options, upload_dir, files) File "/usr/local/bin/post_upload.py", line 209, in ReleaseToCandidatesDir os.chmod(os.path.join(root, d), 0755) OSError: [Errno 2] No such file or directory: '/home/ftp/pub/firefox/nightly/3.6.14-candidates/build1/mac/xpi/.~9h4IDx' Encountered error while uploading Command ['ssh', '-o', 'IdentityFile=~/.ssh/ffxbld_dsa', 'ffxbld@stage.mozilla.org', 'post_upload.py -p firefox -n 1 -v 3.6.14 --release-to-candidates-dir "/tmp/tmp.PwvADA1541/" "/tmp/tmp.PwvADA1541/mac/ko/Firefox 3.6.14.dmg" "/tmp/tmp.PwvADA1541/update/mac/ko/firefox-3.6.14.complete.mar" "/tmp/tmp.PwvADA1541/mac/xpi/ko.xpi"'] returned non-zero exit code: 1
Comment 1•14 years ago
|
||
> Besides the point that it failed I think that we could do something to improve > recovery. > > If a locale fails could we resubmitted as a standalone_repack? This is bug 613970.
Comment 2•14 years ago
|
||
(In reply to comment #1) > > Besides the point that it failed I think that we could do something to improve > > recovery. > > > > If a locale fails could we resubmitted as a standalone_repack? > > This is bug 613970. Should this bug be a dup then?
Updated•14 years ago
|
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → DUPLICATE
Assignee | ||
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
•