Closed
Bug 396095
Opened 17 years ago
Closed 17 years ago
tp-component.zip generation script (from pageloader/ directory)
Categories
(Release Engineering :: General, defect)
Release Engineering
General
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: anodelman, Assigned: bhearsum)
References
Details
Attachments
(2 files, 3 obsolete files)
2.44 KB,
text/plain
|
Details | |
3.20 KB,
patch
|
anodelman
:
review+
|
Details | Diff | Splinter Review |
This script takes the contents of mozilla/layout/tools/pageloader and creates a tp-component.zip archive containing correctly formatted chrome/ and components/ directories. This can be used to have Talos boxes be able to auto-update the pageloader when changes are checked in. If we don't want it all zipped up the script could be altered to simply create chrome/ and components/ directories. I'm not sure if this belongs in the pageloader directory or the talos code, or possibly the buildbot scripts.
Assignee | ||
Comment 1•17 years ago
|
||
This is a slightly modified version of your script that generates the chrome/ and component/ directories in the current working directory. This is what will be used on the Talos slaves.
Assignee | ||
Comment 2•17 years ago
|
||
This version generates the pageloader properly. I also added a few comments.
Attachment #281199 -
Attachment is obsolete: true
Attachment #281201 -
Flags: review?(anodelman)
Reporter | ||
Comment 3•17 years ago
|
||
If run twice in a row you run into this problem: Traceback (most recent call last): File "buildpl.py", line 45, in ? os.mkdir(os.path.join(working_dir, 'chrome')) OSError: [Errno 17] File exists: './chrome' This would be because the chrome/component directories aren't cleaned up between runs. Will this affect functionality with buildbot? Is buildbot handling the cleanup?
Assignee | ||
Comment 4•17 years ago
|
||
Buildbot is handling the clean-up, though that should probably be handled more gracefully. I'll put up a nicer version tomorrow.
Assignee | ||
Comment 5•17 years ago
|
||
This version works exactly like the last one but bails if chrome/ or components/ exists in the working_dir. It will also bail if the cvs checkout fails.
Attachment #281201 -
Attachment is obsolete: true
Attachment #281306 -
Flags: review?(anodelman)
Attachment #281201 -
Flags: review?(anodelman)
Reporter | ||
Updated•17 years ago
|
Attachment #281306 -
Flags: review?(anodelman) → review+
Assignee | ||
Comment 6•17 years ago
|
||
I keep missing this when I go through my bugs so I'm going to assign it to me.
Assignee: nobody → bhearsum
Assignee | ||
Comment 7•17 years ago
|
||
Here's an updated version that uses cvs-mirror by default. I'm proposing that we put it in talos/page_load_test. I think it belongs with Talos as it will be very useful for stand-alone Talos. Not to mention it makes the Buildbot configuration a bit shorter.
Attachment #281306 -
Attachment is obsolete: true
Attachment #281753 -
Flags: review?(anodelman)
Reporter | ||
Comment 8•17 years ago
|
||
Comment on attachment 281753 [details] [diff] [review] same as before, with cvs-mirror.m.o and patchification Thanks for th cvs-mirror change. It will make it simpler for other users to generate chrome/component directories.
Attachment #281753 -
Flags: review?(anodelman) → review+
Reporter | ||
Comment 9•17 years ago
|
||
This was checked in as part of bug 395819. RCS file: /cvsroot/mozilla/tools/buildbot-configs/testing/talos/perfmaster/scripts/generate-tpcomponent.py,v done Checking in scripts/generate-tpcomponent.py; /cvsroot/mozilla/tools/buildbot-configs/testing/talos/perfmaster/scripts/generate-tpcomponent.py,v <-- generate-tpcomponent.py initial revision: 1.1
Status: NEW → RESOLVED
Closed: 17 years ago
Resolution: --- → FIXED
Comment 10•16 years ago
|
||
Mass move of Core:Testing bugs to mozilla.org:ReleaseEngineering. Filter on RelEngMassMove to ignore.
Component: Testing → Release Engineering
Product: Core → mozilla.org
QA Contact: testing → release
Version: Trunk → other
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
•