Closed
Bug 597087
Opened 15 years ago
Closed 14 years ago
Setup project branch for devtools repo
Categories
(Release Engineering :: General, defect, P3)
Release Engineering
General
Tracking
(Not tracked)
VERIFIED
FIXED
People
(Reporter: rcampbell, Assigned: lsblakk)
References
Details
(Whiteboard: [newbranch])
Attachments
(5 files, 1 obsolete file)
|
10.95 KB,
patch
|
catlee
:
review+
|
Details | Diff | Splinter Review |
|
11.03 KB,
patch
|
catlee
:
review+
|
Details | Diff | Splinter Review |
|
1.15 KB,
patch
|
catlee
:
review+
|
Details | Diff | Splinter Review |
|
2.33 KB,
patch
|
rail
:
review+
lsblakk
:
checked-in+
|
Details | Diff | Splinter Review |
|
16.43 KB,
patch
|
rail
:
review+
lsblakk
:
checked-in+
|
Details | Diff | Splinter Review |
We'd like some set of unittests and talos runs for this repo. Not sure if
we need the full suite or not, but definitely mochitest-browser-chrome in opt
and debug configurations
| Reporter | ||
Comment 1•15 years ago
|
||
bug 597008 is now closed and we have a populated repository at hg.mozilla.org/devtools. We're ready for some unittests!
OS: Mac OS X → All
Hardware: x86 → All
Comment 2•15 years ago
|
||
Can you tell us how to run these? What do we need to checkout / download / unpack, and where? What commands then need to be run? How are results reported?
| Reporter | ||
Comment 3•15 years ago
|
||
these are the same mochitests and browser-chrome tests you're running on mozilla-central. In fact, this is mozilla-central + a few changesets. It is a straight copy.
If time is an issue, we can probably get away with just mochitest-browser-chrome for starters. Then full mochitest+xpc_shell followed by talos.
checkout and build is the same, but you'll be pulling from hg.mozilla.org/devtools instead of /mozilla-central.
Comment 4•15 years ago
|
||
Do we need to do a whole new build for this? Is what you really want a new project branch?
| Reporter | ||
Comment 5•15 years ago
|
||
Yes.
Comment 6•15 years ago
|
||
Then please fill out our handy dandy project branch questionnaire!
https://wiki.mozilla.org/ReleaseEngineering:ProjectBranchPlanning
What's the timeline for needing this up and running?
| Reporter | ||
Comment 7•15 years ago
|
||
* Name of hg repo for this branch (relative to hg.mozilla.com)
/devtools
** '''NOTE''': this name will be used for all things related to the branch, tinderbox, tbpl, ftp locations, etc.
** Has a bug already been filed to create the repo?
** Name of parent branch?
tip
* Do you want builds?
yes.
** All o.s. or subset of linux32, linux64, osx10.5, osx10.6, win32, win64
All, but only one flavor of OS X (10.6). Win7 only.
(except mobile, e.g., maemo, android, ... any others?)
** Incremental-build-on-checkin? y/N
yes
** Nightly builds? Y/n
yes
*** Nightly updates? y/N
no
* Do you want unittests?
yes
** All o.s. or subset of: WinXP, Win7, 10.5, 10.6, fedora12, fedora12-64,
all (except as above, only 10.6, win7, no mobile)
* Do you need mobile builds?
no
(note. maybe move this section up to the "Do you want builds" part to prevent people from repeating themselves in the future)
* Do you want talos?
yes
** Do you need talos on Tiger?
Tiger? The OS X release? No, Snow Leopard should be fine.
** All o.s. or subset of Talos platforms?
all (except as above, only 10.6, win7, no mobile)
* Name of the contact person for this branch who will:
** Be doing periodic refreshes from parent
Rob Campbell
** Be contact person for misc setup questions
Rob Campbell
** Decide when to land back project branch onto parent
Rob Campbell
** Decide when to terminate the project branch
Rob Campbell
* Timeline:
** Is this branch is needed for a specific hard calendar deadline? (we typically can do this in 2 weeks, and we will notify you if we think we'll miss that)
We need this for Q4 work, so sooner is better. If 2 weeks is how long it should take, that should be fine, plus any additional padding you require to clear current work.
** For changes in schedule, or status checks, please ping in bug.
** Approx expected life span of project branch - if known?
Ongoing.
* Additional requests:
** By default project branches do not have l10n:
no l10n.
** Need any changes to toolchain used in parent branch?
no
** Need any changes to the compile/link/repack steps used in parent branch?
no
** Do you expect to create any releases from this project branch?
no, builds are for test-only.
*** '''NOTE''': Currently we do not have nightly/alpha/beta/release updates on these project branches.
** Any other info that might be helpful to us?
This is mozilla-central + some set of front-end patches for the browser. Other than repo, it should be a straight copy.
Updated•15 years ago
|
Priority: -- → P3
Summary: Setup buildbot unittests and talos for devtools repo → Setup project branch for devtools repo
Whiteboard: [newbranch]
| Reporter | ||
Comment 8•14 years ago
|
||
Ping. This is going to be needed soon.
| Reporter | ||
Comment 9•14 years ago
|
||
Re-ping! Can I get an ETA on test infrastructure?
| Reporter | ||
Updated•14 years ago
|
Whiteboard: [newbranch] → [newbranch][looking for ETA]
| Assignee | ||
Comment 10•14 years ago
|
||
I'll put together configs for review - aiming for going live by Friday
Assignee: nobody → lsblakk
| Assignee | ||
Comment 11•14 years ago
|
||
So a couple of changes had to be made in order to
a) take macosx out of the possible slave_platforms on talos
b) turn off mobile and enable nightlies for this branch (not previously used on any other project branch yet)
I realize it's a bit hacky, but I also hope that some parts will be useful in bug 633054
Also, a Tinderbox page has been created for this branch in Devtools
Attachment #519324 -
Flags: review?(catlee)
| Assignee | ||
Updated•14 years ago
|
Whiteboard: [newbranch][looking for ETA] → [newbranch]
| Assignee | ||
Comment 12•14 years ago
|
||
Attachment #519327 -
Flags: review?(catlee)
Updated•14 years ago
|
Attachment #519327 -
Flags: review?(catlee) → review+
Comment 13•14 years ago
|
||
Comment on attachment 519324 [details] [diff] [review]
add devtools branch to buildbot-configs
>+# Copy project branches into BRANCHES keys
>+for key, value in PROJECT_BRANCHES.items():
>+ BRANCHES[key] = value
>+
>+# Look for project branch overrides of slave platforms
>+for branch, branch_config in PROJECT_BRANCHES.items():
>+ if branch_config.has_key('platforms'):
>+ for platform in branch_config['platforms']:
>+ if branch_config['platforms'][platform].has_key('slave_platforms') and '-debug' not in platform:
>+ PLATFORMS[platform]['slave_platforms'] = branch_config['platforms'][platform]['slave_platforms']
>+
I think it would be safer to copy the list of slave_platforms here rather than just assigning the same list.
>diff --git a/mozilla/config.py b/mozilla/config.py
>--- a/mozilla/config.py
>+++ b/mozilla/config.py
>@@ -729,16 +729,20 @@
> for key, value in PROJECT_BRANCHES.items():
> BRANCHES[key] = value
>
> # Copy global vars in first, then platform vars
> for branch in BRANCHES.keys():
> for key, value in GLOBAL_VARS.items():
> # Don't override platforms if it's set
> if key == 'platforms' and 'platforms' in BRANCHES[branch]:
>+ # Remove any talos-only platforms from the 'platforms'
>+ for platform in BRANCHES[branch]['platforms'].keys():
>+ if platform not in PLATFORM_VARS.keys():
>+ del BRANCHES[branch]['platforms'][platform]
> continue
> elif key == 'mobile_platforms' and 'mobile_platforms' in BRANCHES[branch]:
> continue
> BRANCHES[branch][key] = deepcopy(value)
What's this chunk for?
Can you do a pass through dump_master to make sure you're only affecting the new devtools branch?
Attachment #519324 -
Flags: review?(catlee) → review-
| Assignee | ||
Comment 14•14 years ago
|
||
added deepcopying as per comments, also added an is_test check on platforms which are to be used in talos only. also added slave_platforms[] customization (buildbotcustom patch accompanies this) in order to disable the OS 10.5 tests
Attachment #519324 -
Attachment is obsolete: true
Attachment #520370 -
Flags: review?(catlee)
| Assignee | ||
Comment 15•14 years ago
|
||
this will check if a branch_config has ['slave_platforms'] set first before grabbing the ACTIVE_PLATFORMS ones so that we can customize which slave_platforms we want at the branch level, namely in project_branches.
Attachment #520371 -
Flags: review?(catlee)
| Assignee | ||
Comment 16•14 years ago
|
||
OK so I ran dump_masters on an instance of a builder master, build-scheduler, test-scheduler, and test master -- all of them are only affected by having new devtools builders in them. Here's the example of the build-scheduler:
--- dump_master 2011-03-21 15:46:29.437419035 -0700
+++ dump_master_devtools 2011-03-21 15:46:14.663831380 -0700
@@ -21,6 +21,7 @@
<buildbotcustom.changes.hgpoller.HgPoller object> 'http://hg.mozilla.org/services/services-central/json-pushes?full=1' {'branch': 'services/services-central',
'hgURL': 'http://hg.mozilla.org/',
'pollInterval': 60}
+<buildbotcustom.changes.hgpoller.HgPoller object> 'http://hg.mozilla.org/devtools/json-pushes?full=1' {'branch': 'devtools', 'hgURL': 'http://hg.mozilla.org/', 'pollInterval': 60}
<buildbotcustom.changes.hgpoller.HgPoller object> 'http://hg.mozilla.org/projects/maple/json-pushes?full=1' {'branch': 'projects/maple',
'hgURL': 'http://hg.mozilla.org/',
'pollInterval': 60}
@@ -447,6 +448,51 @@
'name': 'mobile-browser-services-central-build-mobile',
'properties': {'scheduler': 'mobile-browser-services-central-build-mobile'},
'treeStableTimer': 180}
+<buildbotcustom.scheduler.Scheduler-props> {'builderNames': ['Linux QT devtools build',
+ 'OS X 10.5.2 devtools build',
+ 'OS X 10.6.2 devtools build',
+ 'WINNT 5.2 devtools build',
+ 'Linux x86-64 devtools build',
+ 'Linux devtools build',
+ 'WINNT 5.2 devtools leak test build',
+ 'OS X 10.6.2 devtools leak test build',
+ 'Linux x86-64 devtools leak test build',
+ 'Linux devtools leak test build'],
+ 'change_filter': <ChangeFilter on branch == devtools>,
+ 'fileIsImportant': <function <lambda>>,
+ 'name': 'devtools',
+ 'properties': {'scheduler': 'devtools'},
+ 'propfuncs': [<function buildIDSchedFunc>,
+ <function buildUIDSchedFunc>],
+ 'treeStableTimer': 180}
+<buildbotcustom.scheduler.SpecificNightly-props> {'branch': 'devtools',
+ 'builderNames': ['OS X 10.5.2 devtools nightly',
+ 'OS X 10.6.2 devtools nightly',
+ 'WINNT 5.2 devtools nightly',
+ 'Linux x86-64 devtools nightly',
+ 'Linux devtools nightly'],
+ 'dayOfMonth': '*',
+ 'dayOfWeek': '*',
+ 'fileIsImportant': None,
+ 'hour': [4],
+ 'minute': [2],
+ 'month': '*',
+ 'name': 'devtools nightly',
+ 'onlyIfChanged': False,
+ 'properties': {'scheduler': 'devtools nightly'},
+ 'propfuncs': [<function buildIDSchedFunc>,
+ <function buildUIDSchedFunc>]}
+<buildbot.schedulers.timed.Nightly> {'branch': 'devtools',
+ 'builderNames': [],
+ 'dayOfMonth': '*',
+ 'dayOfWeek': 5,
+ 'fileIsImportant': None,
+ 'hour': [3],
+ 'minute': [2],
+ 'month': '*',
+ 'name': 'weekly-devtools',
+ 'onlyIfChanged': False,
+ 'properties': {'scheduler': 'weekly-devtools'}}
<buildbotcustom.scheduler.Scheduler-props> {'builderNames': ['Linux QT maple build',
'OS X 10.6.2 maple build',
'WINNT 5.2 maple build',
Updated•14 years ago
|
Attachment #520370 -
Flags: review?(catlee) → review+
Updated•14 years ago
|
Attachment #520371 -
Flags: review?(catlee) → review+
| Assignee | ||
Comment 17•14 years ago
|
||
This branch is now live in production. Please start using it and reopen this bug if any issues arise regarding its setup.
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → FIXED
Comment 18•14 years ago
|
||
(In reply to comment #17)
> This branch is now live in production. Please start using it and reopen this
> bug if any issues arise regarding its setup.
Hawt! Thank you.
| Assignee | ||
Comment 19•14 years ago
|
||
Looking into burning on the linux opt * and the mac10.5 nightly SDK issue.
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
| Assignee | ||
Comment 20•14 years ago
|
||
Attachment #521024 -
Flags: review?(rail)
| Assignee | ||
Comment 21•14 years ago
|
||
Attachment #521025 -
Flags: review?(rail)
Updated•14 years ago
|
Attachment #521024 -
Flags: review?(rail) → review+
Updated•14 years ago
|
Attachment #521025 -
Flags: review?(rail) → review+
| Assignee | ||
Comment 22•14 years ago
|
||
Comment on attachment 521025 [details] [diff] [review]
fixes devtools (and any branch with overriden platforms) to not need to be in the PLATFORMS list
landed on default http://hg.mozilla.org/build/buildbotcustom/rev/076e569f00bb
Attachment #521025 -
Flags: checked-in+
| Assignee | ||
Comment 23•14 years ago
|
||
Comment on attachment 521024 [details] [diff] [review]
fix devtools by adding to list of gcc bug fix branches, and removing uneeded macosx 10.5
landed on default http://hg.mozilla.org/build/buildbot-configs/rev/341cc4cfabb5
Attachment #521024 -
Flags: checked-in+
| Assignee | ||
Comment 24•14 years ago
|
||
FYI - because of release mechanics right now this isn't landing today but as soon as it does the burning on linuc & macosx 10.5 will go away. Know that this is in our deployment queue and will go out on the next reconfig which should happen in the next day or two.
| Reporter | ||
Comment 25•14 years ago
|
||
sounds good. Thanks for your help!
| Reporter | ||
Comment 26•14 years ago
|
||
any estimate when we can land this? We have patches we'd like to land on this branch now and can't do so until we get some greenery.
| Assignee | ||
Comment 27•14 years ago
|
||
the reconfig is happening as i write this, so within the next 20 minutes all production masters should have these updates.
| Assignee | ||
Comment 28•14 years ago
|
||
looks like we're good to go now - closing again.
Status: REOPENED → RESOLVED
Closed: 14 years ago → 14 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
•