Closed
Bug 863428
Opened 13 years ago
Closed 13 years ago
Misleading line in log file of final verification
Categories
(Release Engineering :: Release Automation, defect)
Release Engineering
Release Automation
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: pmoore, Assigned: pmoore)
References
Details
Attachments
(1 file)
|
1.24 KB,
patch
|
bhearsum
:
review+
bhearsum
:
checked-in+
|
Details | Diff | Splinter Review |
In the final verification report this week (http://10.134.49.62:8001/builders/release-mozilla-beta-final_verification/builds/0/steps/final_verification/logs/stdio) it said:
Wed Apr 17 05:14:14 PDT 2013: Mar files found: 26987
The mar files at this point have not been uniquely sorted - so this is the total number of mar file urls read from the update.xml files. The actual number of unique mar urls is far lower - 1087. This can be deduced by counting the number of lines "Mar file xxxxx available with correct size (yyyyy bytes)" in the log file. The attached patch resolves this issue. Please note, this bug only affects this logging line - this does not affect the checks - the checks are running properly.
Updated•13 years ago
|
Component: Release Engineering → Release Engineering: Automation (Release Automation)
QA Contact: bhearsum
| Assignee | ||
Comment 1•13 years ago
|
||
Attachment #739251 -
Flags: review?(bhearsum)
Comment 2•13 years ago
|
||
Comment on attachment 739251 [details] [diff] [review]
Proposed patch for build tools repo
Review of attachment 739251 [details] [diff] [review]:
-----------------------------------------------------------------
Seems fine. You mentioned on IRC earlier that were some mar URLs that didn't appear in the log that you expected to be there. Did you track down what happened with those?
Attachment #739251 -
Flags: review?(bhearsum) → review+
| Assignee | ||
Comment 3•13 years ago
|
||
Hi Ben,
Not yet. I've created a separate bug for that - bug 863602.
Thanks,
Pete
Updated•13 years ago
|
Attachment #739251 -
Flags: checked-in+
| Assignee | ||
Updated•13 years ago
|
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
Updated•12 years ago
|
Product: mozilla.org → Release Engineering
You need to log in
before you can comment on or make changes to this bug.
Description
•