Closed
Bug 632399
Opened 14 years ago
Closed 13 years ago
xulrunner linux builds do not need the ctor steps
Categories
(Release Engineering :: Release Automation: Other, defect, P4)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: armenzg, Unassigned)
References
Details
(Whiteboard: [releases])
I noticed that we only run these steps for the the linux xulrunner build:
http://hg.mozilla.org/build/buildbotcustom/file/tip/process/factory.py#l849
* get_ctors set props: testresults num_ctors ( 0 secs )
* tinderboxprint_ctors tinderboxprint_ctors ( 0 secs )
I don't know where these two steps come from:
* setproperty set props: buildid ( 0 secs )
* setproperty_1 set props: sourcestamp ( 0 secs )
Comment 1•14 years ago
|
||
(In reply to comment #0)
> I noticed that we only run these steps for the the linux xulrunner build:
>
> http://hg.mozilla.org/build/buildbotcustom/file/tip/process/factory.py#l849
> * get_ctors set props: testresults num_ctors ( 0 secs )
> * tinderboxprint_ctors tinderboxprint_ctors ( 0 secs )
>
> I don't know where these two steps come from:
> * setproperty set props: buildid ( 0 secs )
> * setproperty_1 set props: sourcestamp ( 0 secs )
I think it's possibly useful to run the steps (they've been running for months), we just don't need to gather properties for the graph server post, which is what broke.
Reporter | ||
Updated•14 years ago
|
Priority: -- → P4
Whiteboard: [releases]
Updated•13 years ago
|
Blocks: hg-automation
Updated•13 years ago
|
No longer blocks: hg-automation
Comment 2•13 years ago
|
||
Mass move of bugs to Release Automation component.
Blocks: hg-automation
Component: Release Engineering → Release Engineering: Automation (Release Automation)
Updated•13 years ago
|
No longer blocks: hg-automation
Comment 3•13 years ago
|
||
Doesn't look like these run for XULRunner anymore.
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
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
•