Closed
Bug 830466
Opened 13 years ago
Closed 13 years ago
Trigger spidermonkey try builds based on all file changes, not just tip changes
Categories
(Release Engineering :: General, defect)
Release Engineering
General
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: sfink, Assigned: sfink)
Details
Attachments
(1 file)
|
1.39 KB,
patch
|
catlee
:
review+
sfink
:
checked-in+
|
Details | Diff | Splinter Review |
Currently, only the tip revision of a push is checked for changes to js/src in order to decide whether to trigger spidermonkey try jobs.
|
Assignee | |
Comment 1•13 years ago
|
||
From ted & catlee on IRC, it sounds like tipsOnly was turned on for try to resolve a load issue (timeouts when polling try), but that *should* no longer be an issue now that (1) we have json-pushes, which no longer loses the assignment of changesets to pushes; and (2) this patch also turns on mergePushChanges, which caps the number of changes that will get rolled up into one pseudo-changeset.
This change makes HgPoller behavior more uniform for try and non-try, which may reduce confusion.
Attachment #701922 -
Flags: review?(catlee)
|
||
Updated•13 years ago
|
Attachment #701922 -
Flags: review?(catlee) → review+
|
|
Assignee | |
Updated•13 years ago
|
Attachment #701922 -
Flags: checked-in+
|
|
Assignee | |
Comment 2•13 years ago
|
||
|
|
||
Comment 3•13 years ago
|
||
in production
|
|
Assignee | |
Updated•13 years ago
|
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
|
||
Updated•13 years ago
|
Product: mozilla.org → Release Engineering
|
|
||
Updated•8 years ago
|
Component: General Automation → General
You need to log in
before you can comment on or make changes to this bug.
Description
•