Closed Bug 632399 Opened 9 years ago Closed 8 years ago

xulrunner linux builds do not need the ctor steps

Categories

(Release Engineering :: Release Automation: Other, defect, P4)

x86
macOS
defect

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 )
(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.
Priority: -- → P4
Whiteboard: [releases]
No longer blocks: hg-automation
Mass move of bugs to Release Automation component.
Component: Release Engineering → Release Engineering: Automation (Release Automation)
No longer blocks: hg-automation
Doesn't look like these run for XULRunner anymore.
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → FIXED
Product: mozilla.org → Release Engineering
You need to log in before you can comment on or make changes to this bug.