Closed
Bug 418870
Opened 16 years ago
Closed 16 years ago
setup talos to test moz2 builds
Categories
(Release Engineering :: General, defect, P2)
Release Engineering
General
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: bhearsum, Assigned: anodelman)
References
Details
Attachments
(6 files)
15.04 KB,
patch
|
bhearsum
:
review+
|
Details | Diff | Splinter Review |
26.07 KB,
patch
|
rcampbell
:
review+
|
Details | Diff | Splinter Review |
25.93 KB,
patch
|
rcampbell
:
review+
|
Details | Diff | Splinter Review |
40.57 KB,
patch
|
rcampbell
:
review+
|
Details | Diff | Splinter Review |
8.84 KB,
patch
|
rcampbell
:
review+
|
Details | Diff | Splinter Review |
8.81 KB,
patch
|
bhearsum
:
review+
|
Details | Diff | Splinter Review |
Assignee | ||
Updated•16 years ago
|
Assignee: nobody → anodelman
OS: Mac OS X → All
Hardware: PC → All
Reporter | ||
Comment 1•16 years ago
|
||
OK. There's currently mozilla-central + actionmonkey builds for Linux and Win32. All of the win32 builds are busted right now but that shouldn't necessarily stop you from getting the infra up. mozilla-central builds are here: ftp://ftp.mozilla.org/pub/mozilla.org/firefox/tinderbox-builds/mozilla-central-linux/ ftp://ftp.mozilla.org/pub/mozilla.org/firefox/tinderbox-builds/mozilla-central-win32/ ftp://ftp.mozilla.org/pub/mozilla.org/firefox/tinderbox-builds/actionmonkey-linux/ ftp://ftp.mozilla.org/pub/mozilla.org/firefox/tinderbox-builds/actionmonkey-win32/ (The last directory doesn't exist yet, because it's never had a working build). The names of the builders are on the Mozilla2 tinderbox tree (http://tinderbox.mozilla.org/showbuilds.cgi?tree=Mozilla2). I think this is all of the information you'll need.
Assignee | ||
Comment 2•16 years ago
|
||
I'm assuming that there are probably problems in here having to do with the scheduler, since I haven't set one up from scratch before. The build steps/factories should be fine as they are mostly copies of the existing linux set up.
Attachment #306333 -
Flags: review?(bhearsum)
Reporter | ||
Comment 3•16 years ago
|
||
Comment on attachment 306333 [details] [diff] [review] first attempt at setting up staging actionmonkey/mozilla central linux talos >Index: master.cfg >+LINUX_MOZ2_CENTRAL_BUILDER="mozilla-central-linux" >+LINUX_MOZ2_CENTRAL_BUILDDIR="http://ftp.mozilla.org/pub/mozilla.org/firefox/tinderbox-builds/mozilla-central-linux/" >+LINUX_MOZ2_ACTIONMONKEY_BUILDER="actionmonkey-linux" >+LINUX_MOZ2_ACTIONMONKEY_BUILDDIR="http://ftp.mozilla.org/pub/mozilla.org/firefox/tinderbox-builds/actionmonkey-linux/" Looking at this again, I don't know why I gave you links to ftp.m.o, this should be stage.m.o as it takes time for stage to sync to ftp. >+ "Linux talos moz2 (mozilla central)", >+ "Linux talos moz2 (actionmonkey)", I think these could just be 'Linux talos mozilla-central' and 'Linux talos actionmonkey'. Doesn't really matter though. Other than those minor things this looks fine.
Reporter | ||
Comment 4•16 years ago
|
||
Comment on attachment 306333 [details] [diff] [review] first attempt at setting up staging actionmonkey/mozilla central linux talos r+ with those changes
Attachment #306333 -
Flags: review?(bhearsum) → review+
Assignee | ||
Comment 5•16 years ago
|
||
Checking in master.cfg; /cvsroot/mozilla/tools/buildbot-configs/testing/talos/perfmaster/master.cfg,v <-- master.cfg new revision: 1.40; previous revision: 1.39 done
Assignee | ||
Updated•16 years ago
|
Assignee: anodelman → nobody
Component: Testing → Release Engineering
Priority: -- → P2
Product: Core → mozilla.org
QA Contact: testing → release
Version: Trunk → other
Assignee | ||
Updated•16 years ago
|
Assignee: nobody → anodelman
Assignee | ||
Comment 6•16 years ago
|
||
Attachment #310101 -
Flags: review?(rcampbell)
Assignee | ||
Updated•16 years ago
|
Comment 7•16 years ago
|
||
Comment on attachment 310101 [details] [diff] [review] staging configuration for mac/win moz2 machines looks good
Attachment #310101 -
Flags: review?(rcampbell) → review+
Assignee | ||
Comment 8•16 years ago
|
||
Staging configuration for mac/win moz2 machines Checking in master.cfg; /cvsroot/mozilla/tools/buildbot-configs/testing/talos/perf-staging/master.cfg,v <-- master.cfg new revision: 1.4; previous revision: 1.3 done
Assignee | ||
Comment 9•16 years ago
|
||
There are now win, mac & linux moz2 testers reporting to MozillaTest.
Assignee | ||
Comment 10•16 years ago
|
||
These machines are successfully cycling and reporting to MozillaTest - they can now be moved to the Mozilla2 waterfall. This patch is for mozilla-central only, actionmonkey will remain in staging.
Attachment #313194 -
Flags: review?(rcampbell)
Comment 11•16 years ago
|
||
Comment on attachment 313194 [details] [diff] [review] push mozilla-central talos machines to production what's a "MultiBuildScheduler" and where does it get installed?
Reporter | ||
Comment 12•16 years ago
|
||
MultiBuildScheduler will trigger a build X number of times instead of only 1. I was hoping it could go into buildbotcustom (this would require a checkout of buildbotcustom on the talos master).
Updated•16 years ago
|
Attachment #313194 -
Flags: review?(rcampbell) → review+
Assignee | ||
Comment 13•16 years ago
|
||
Push mozilla-central to production: Checking in master.cfg; /cvsroot/mozilla/tools/buildbot-configs/testing/talos/perfmaster/master.cfg,v <-- master.cfg new revision: 1.51; previous revision: 1.50 done
Assignee | ||
Comment 14•16 years ago
|
||
Backed out the patch, wouldn't apply to talos buildbot master with: File "/home/buildbot/builds/lib/python2.4/site-packages/buildbot/master.py", line 684, in loadConfig for name, passwd in bots: exceptions.ValueError: too many values to unpack Have we hit the upper limit of the amount of bots allowed for a master? Or is this just some typo in the bots list that I'm not noticing...
Assignee | ||
Comment 15•16 years ago
|
||
Push mozilla-central to production take 2: Checking in master.cfg; /cvsroot/mozilla/tools/buildbot-configs/testing/talos/perfmaster/master.cfg,v <-- master.cfg new revision: 1.53; previous revision: 1.52 done
Comment 16•16 years ago
|
||
This is done for mozilla-central, so removing blocking status... leaving this open for actionmonkey.
No longer blocks: 422754
Assignee | ||
Comment 17•16 years ago
|
||
Current status of actionmonkey: - 3 linux machines testing - 3 mac tiger machines testing Blocking on winxp machines because we are currently not successfully generating actionmonkey builds on winxp for testing.
Comment 18•16 years ago
|
||
updated during triage.
Assignee | ||
Comment 19•16 years ago
|
||
In the interest of finishing up the talos set up I've temporarily hooked up the win32 actionmonkey testers to mozilla-central builds - this will help assure us that the machines are correctly configured so that once win32 actionmonkey builds become available we'll be ready to go. Once the configuration has been assured on all platforms these machines can be pushed to production.
Assignee | ||
Comment 20•16 years ago
|
||
Even though we are not producing actionmonkey windows builds I've testing the talos configuration on the win talos boxes with mozilla-central builds - so they'll be ready once builds become available. The numbers for the linux/mac actionmonkey machines are also stable and ready to go.
Attachment #320045 -
Flags: review?(rcampbell)
Updated•16 years ago
|
Attachment #320045 -
Flags: review?(rcampbell) → review+
Assignee | ||
Comment 21•16 years ago
|
||
Checking in perfmaster/master.cfg; /cvsroot/mozilla/tools/buildbot-configs/testing/talos/perfmaster/master.cfg,v <-- master.cfg new revision: 1.55; previous revision: 1.54 done Checking in perf-staging/master.cfg; /cvsroot/mozilla/tools/buildbot-configs/testing/talos/perf-staging/master.cfg,v <-- master.cfg new revision: 1.11; previous revision: 1.10 done
Comment 22•16 years ago
|
||
From moz2 meeting this week: 1) It going to take at least a couple of weeks to resolve bug#428529. 2) Its sufficient to take the talos machines setup for actionmonkey, reassign them to mozilla-central, confirm they work ok, and then reassign them back to the broken actionmonkey branch. With those experiments done, people were fine with removing blocking dependency on bug#428529. At that point, we can close this bug#418870. 3) Once the actionmonkey branch works again, the talos machines will see the actionmonkey builds and start testing them. As we know the same machines work on mozilla-central, any differences in behavior will be investigated by the actionmonkey folks.
No longer depends on: 428529
Whiteboard: waiting on blockers
Assignee | ||
Comment 23•16 years ago
|
||
All the machines that are currently up are now reporting to the Mozilla2 waterfall.
Assignee | ||
Comment 24•16 years ago
|
||
Now working on setting up - mozilla-central vista machines - mozilla-central leopard machines - mozilla-central nochrome testers on all platforms That should pretty much cover all the necessary machines for complete talos coverage of mozilla-central.
Assignee | ||
Updated•16 years ago
|
Priority: P3 → P2
Assignee | ||
Comment 25•16 years ago
|
||
I've split out the nochrome/fast cycle moz2 machines into bug 436368. This bug covers the primary talos support for moz2 - talos triads on all five platforms. We'll consider this bug completed when the vista & leopard talos sets are pushed to production.
Assignee | ||
Comment 26•16 years ago
|
||
Attachment #322991 -
Flags: review?(rcampbell)
Comment 27•16 years ago
|
||
Comment on attachment 322991 [details] [diff] [review] push mozilla-central vista talos machines to production mysterious extra line in the Status comment section. Otherwise, cromulent.
Attachment #322991 -
Flags: review?(rcampbell) → review+
Assignee | ||
Comment 28•16 years ago
|
||
Removed mysterious extra line. Checking in master.cfg; /cvsroot/mozilla/tools/buildbot-configs/testing/talos/perfmaster/master.cfg,v <-- master.cfg new revision: 1.60; previous revision: 1.59 done
Assignee | ||
Comment 29•16 years ago
|
||
Attachment #323134 -
Flags: review?(rcampbell)
Assignee | ||
Updated•16 years ago
|
Attachment #323134 -
Flags: review?(rcampbell) → review?(bhearsum)
Reporter | ||
Comment 30•16 years ago
|
||
Comment on attachment 323134 [details] [diff] [review] push mozilla-central leopard talos machines to production happy friday!
Attachment #323134 -
Flags: review?(bhearsum) → review+
Assignee | ||
Comment 31•16 years ago
|
||
Checking in master.cfg; /cvsroot/mozilla/tools/buildbot-configs/testing/talos/perfmaster/master.cfg,v <-- master.cfg new revision: 1.61; previous revision: 1.60 done
Assignee | ||
Comment 32•16 years ago
|
||
Status update: - fast cycle machine currently reporting to talos stage - nochrome machines blocked on racking/imaging of newly purchased minis
Assignee | ||
Comment 33•16 years ago
|
||
- nochrome machines up and reporting. All done here.
Group: mozilla-confidential
Status: NEW → RESOLVED
Closed: 16 years ago
Resolution: --- → FIXED
Updated•15 years ago
|
Group: mozilla-confidential
Component: Release Engineering: Talos → Release Engineering
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
•