Closed
Bug 602120
Opened 14 years ago
Closed 14 years ago
set up a new staging and production mobile master using 'mobile' configs running under buildbot 0.8.0
Categories
(Release Engineering :: General, defect)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: jhford, Assigned: jhford)
References
Details
(Whiteboard: [mobile])
Attachments
(1 file)
(deleted),
patch
|
mozilla
:
review+
|
Details | Diff | Splinter Review |
This is needed to have the devices that are reimaged for bug 602119 to work properly. I proposed setting this up on the existing machine on port 9010 along side the current production-mobile-master running on port 9020.
Assignee | ||
Comment 2•14 years ago
|
||
working on this.
Assignee: nobody → jhford
Status: NEW → ASSIGNED
Whiteboard: [mobile]
Assignee | ||
Comment 3•14 years ago
|
||
This bug is now for getting the staging environment up and running as well as installing dependencies for the production instance. This bug is not to track moving the production pool to the new buildbot version
Summary: set up a new production mobile master using 'mobile' configs running under buildbot 0.8.0 → set up a new staging and production mobile master using 'mobile' configs running under buildbot 0.8.0
Assignee | ||
Comment 4•14 years ago
|
||
setting up the master with: wget http://www.python.org/ftp/python/2.6.5/Python-2.6.5.tar.bz2 tar jxf Python-2.6.5.tar.bz2 cd Python-2.6.5 ./configure --prefix=/tools/python-2.6.5 make -j4 sudo make install wget http://pypi.python.org/packages/source/v/virtualenv/virtualenv-1.5.1.tar.gz#md5=3daa1f449d5d2ee03099484cecb1c2b7 PYTHONHOME=/tools/python-2.6.5/ /tools/python-2.6.5/bin/python2.6 setup.py install cd /builds/buildbot PYTHONHOME=/tools/python-2.6.5 /tools/python-2.6.5/bin/virtualenv staging-mobile-master cd staging-mobile-master source bin/activate hg clone http://hg.mozilla.org/build/buildbot-configs hg clone http://hg.mozilla.org/build/buildbotcustom hg clone http://hg.mozilla.org/build/buildbot hg clone http://hg.mozilla.org/build/twisted cd lib/python2.6/site-packages ln -s ../../../buildbotcustom cd twisted python2.6 setup.py install cd ../buildbot/master python2.6 setup.py install cd /builds/buildbot/staging-mobile-master ./bin/buildbot create-master master cd master ln -s ../buildbot-configs/mobile/config-production.py ln -s ../buildbot-configs/mobile/config-staging.py ln -s ../buildbot-configs/mobile/defaults.py ln -s ../buildbot-configs/mobile/master.cfg ln -s config-staging.py config.py cd /builds/buildbot/staging-mobile-master #create makefile echo > Makefile << E BUILDBOT=./bin/buildbot PYTHONPATH=master none: @echo Invalid start: PYTHONPATH=$(PYTHONPATH) $(BUILDBOT) start master stop: PYTHONPATH=$(PYTHONPATH) $(BUILDBOT) stop master reconfig: PYTHONPATH=$(PYTHONPATH) $(BUILDBOT) reconfig master checkconfig: PYTHONPATH=$(PYTHONPATH) $(BUILDBOT) checkconfig master/master.cfg make start E #Watch out for tabs instead of spaces
Assignee | ||
Comment 5•14 years ago
|
||
I am running the following devices as staging on PMM:9010 using this master. n900-006 n900-008 n900-010 n900-015 n900-018 n900-020 n900-031 Of these, only 031 has been initialized so far. I am going to be working on the others tonight/tomorrow
Assignee | ||
Updated•14 years ago
|
Assignee | ||
Comment 7•14 years ago
|
||
Comment on attachment 485155 [details] [diff] [review] create pmm:9010 and smm:9010 the bugzilla diff view is slightly flawed in that it doesn't show the copy from mobile/config-production.py copy to mobile/config-production-n900.py and copy from mobile/config-staging.py copy to mobile/config-staging-n900.py lines. It only shows the from file in the diff header.
Comment 8•14 years ago
|
||
Comment on attachment 485155 [details] [diff] [review] create pmm:9010 and smm:9010 I noticed that buildbotcustom:buildbot-0.8.0's process/mobiletestfactory.py is out of date; you may want to just overwrite it with the default version. r+ for that and this.
Attachment #485155 -
Flags: review?(aki) → review+
Assignee | ||
Comment 10•14 years ago
|
||
for some reason, the command that is being sent to the n900s on the new master is not including the --noChrome parameter to perfconfigurator. I am going to double check manually, but I have a feeling that showing browser chrome might be what is causing the browser to freeze on the tests.
Assignee | ||
Comment 11•14 years ago
|
||
confirmed on the command line that this is indeed caused by the missing --noChrome on the command line! Now that I know what's up, I will work on fixing it :D
Assignee | ||
Comment 12•14 years ago
|
||
not sure exactly what is going on, but PerfConfigurator when run on the old configuration with nochrome=False resulted in --noChrome being inserted in a seemingly random location in the command string "--resultsServer graphs.mozilla.org --noChrome --resultsLink" instead of where it should be inserted, at the end of the argv. I am going to try writing a patch that creates a 'nochrome' setting in the test suite dictionary so as not to rename all the builders.
Assignee | ||
Comment 13•14 years ago
|
||
this problem manifests only in pageloader tests, not startup tests.
Assignee | ||
Comment 14•14 years ago
|
||
This was caused by not updating the master after landing code. Updating the real pmm now would cause it to break in the same ways that it is breaking for me on my test master and is not advisable until I have the fix tested + landed. [cltbld@production-mobile-master production-mobile-master]$ hg ident -R /tools/buildbotcustom/buildbotcustom/ .hgtags@5e88d9565da2, line 93: tag 'FIREFOX_3_6_9_BUILD1' refers to unknown node .hgtags@5e88d9565da2, line 94: tag 'FIREFOX_3_6_9_RELEASE' refers to unknown node 5e88d9565da2 tip which is from oct5 2010
Assignee | ||
Comment 15•14 years ago
|
||
The following tests are being run as --noChrome: tdhtml tgfx tpan ts tsspider tsvg twinopen tzoom
Assignee | ||
Comment 16•14 years ago
|
||
nothing left here. These are running at production-mobile-master:8010 staging-mobile-master:8010
Status: ASSIGNED → RESOLVED
Closed: 14 years ago
Resolution: --- → FIXED
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
•