Closed
Bug 551504
Opened 15 years ago
Closed 15 years ago
put working n900 talos tests in production
Categories
(Release Engineering :: General, defect, P2)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: jhford, Assigned: jhford)
References
Details
Attachments
(1 file, 1 obsolete file)
21.84 KB,
patch
|
mozilla
:
review+
|
Details | Diff | Splinter Review |
We are going to put ts, twinopen, tdhtml, tsvg, tsspider, tgfx in production tracking mozilla-central, mozilla-1.9.2, tracemonkey and electrolysis.
This bug is to track the patches that enable this, creating a buildbot master on production-mobile-master and moving devices over to production.
Assignee | ||
Comment 1•15 years ago
|
||
put the code currently running on SMM into production.
Attachment #431663 -
Flags: review?(aki)
Assignee | ||
Comment 2•15 years ago
|
||
forgot to disable the broken tests in staging as well
Attachment #431663 -
Attachment is obsolete: true
Attachment #431667 -
Flags: review?(aki)
Attachment #431663 -
Flags: review?(aki)
Assignee | ||
Comment 3•15 years ago
|
||
run on PMM:
cd /tools/
hg clone http://hg.mozilla.org/build/buildbotcustom buildbotcustom2
cd /builds/buildbot
hg clone http://hg.mozilla.org/build/buildbot-configs configs2
mkdir mobile-master2
cd ~
wget http://tmrc.mit.edu/mirror/twisted/Twisted/9.0/Twisted-9.0.0.tar.bz2
cd Twisted-9.0.0
python setup.py build
cd ..
mv Twisted-9.0.0 /tools
wget http://downloads.sourceforge.net/buildbot/buildbot-0.7.12.tar.gz
tar zxf buildbot-0.7.12
python setup.py build
cd ..
mv buildbot-0.7.12 /tools
cat > buildbot << EOF
#!/bin/sh
PYTHONPATH=/tools/buildbot-0.7.12/build/lib:/tools/buildbotcustom2:/tools/Twisted-9.0.0/build/lib.linux-i686-2.5/:/tools/zope-interface/lib/python2.5/site-packages/ /tools/buildbot-0.7.12/build/scripts-2.5/buildbot $@
EOF
cd /builds/buildbot/mobile-master2
#buildbot create-master won't work properly, so get public_html from smm2
chmod +x buildbot
./buildbot create-master .
scp -r staging-mobile-master:/builds/buildbot/staging-mobile-master2/public_html .
ln -s ../configs2/mobile-rw/master.cfg
ln -s ../configs2/mobile-rw/config.py
ln -s ../configs2/mobile-rw/defaults.py
./buildbot start
Status: NEW → ASSIGNED
Priority: -- → P2
Assignee | ||
Comment 4•15 years ago
|
||
to move a device over to production you would need to run:
ssh root@n900-NNN sed -i -e 's/BBHOST=.*$/BBHOST="production-mobile-master.build.mozilla.org"/' /etc/mozconf
Comment 5•15 years ago
|
||
Comment on attachment 431667 [details] [diff] [review]
n900 production patches. now with staging updates as well
>+ 'tracemonkey' : {
>+ 'ftp_string': 'mobile-tracemonkey',
>+ 'talos_branch': 'mobile-tracemonkey',
>+ 'tinderbox_tree': 'TraceMonkey',
>+ 'graph_server': 'graphs.mozilla.org',
>+ 'tree_stable_timer': 2,
>+ 'nightly': True,
>+ 'per_checkin': True,
>+ 'platforms': {
>+ 'n900': deepcopy(default_n900),
>+ },
>+ },
We're going to have to figure out how to set unit tests to nightly and talos to per-checkin for tracemonkey. We're also going to have to schedule qt at different rates than gtk. N/A now since unit tests are off and we don't have qt builds to test yet, so feel free to leave this comment for a follow up bug.
>+ 'electrolysis': {
>+ 'ftp_string': 'mobile-electrolysis',
>+ 'talos_branch': 'mobile-electrolysis',
>+ 'tinderbox_tree': 'Electrolysis',
>+ 'graph_server': 'graphs.mozilla.org',
>+ 'tree_stable_timer': 2,
>+ 'nightly': True,
>+ 'per_checkin': True,
electrolysis should be nightly only. Our ftppoller may not actually work in the latest-mobile-* directories, however; we may have to munge a nightly scheduler, use sendchanges, or play with polling intervals til we solve that. We should discuss this fix.
>+ 'places': {
Places isn't on the list, yank it.
Assignee | ||
Comment 6•15 years ago
|
||
(In reply to comment #5)
> We're going to have to figure out how to set unit tests to nightly and talos to
> per-checkin for tracemonkey. We're also going to have to schedule qt at
> different rates than gtk. N/A now since unit tests are off and we don't have
> qt builds to test yet, so feel free to leave this comment for a follow up bug.
for nightly vs. per checkin, we can use the nightly and per_checkin argument, but that does depend on the poller working properly.
I was thinking a quick (and maybe most correct) way to qt specifics is to have qt differentiation done at the branch level instead of platform. We could then use the per_checkin/nightly args.
Sample Config:
'tracemonkey-qt' : {
'ftp_string': 'mobile-tracemonkey-qt',
'talos_branch': 'mobile-tracemonkey-qt',
'tinderbox_tree': 'TraceMonkey',
'graph_server': 'graphs.mozilla.org',
'tree_stable_timer': 2,
'nightly': True,
'per_checkin': True,
'platforms': {
'n900': deepcopy(default_n900),
},
},
> electrolysis should be nightly only. Our ftppoller may not actually work in
> the latest-mobile-* directories, however; we may have to munge a nightly
> scheduler, use sendchanges, or play with polling intervals til we solve that.
> We should discuss this fix.
I general, I think that sendchanges are the way to fix this, but there are definite issues with the sendchange interfacing.
> Places isn't on the list, yank it.
oh right, it has so few checkins that i forgot it existed for a while as no results showed up on tb.
Comment 7•15 years ago
|
||
(In reply to comment #6)
> I was thinking a quick (and maybe most correct) way to qt specifics is to have
> qt differentiation done at the branch level instead of platform.
Makes sense.
r=me with electrolysis->nightly, places removed.
Updated•15 years ago
|
Attachment #431667 -
Flags: review?(aki) → review+
Assignee | ||
Comment 8•15 years ago
|
||
this has been landed and is running fine
Status: ASSIGNED → RESOLVED
Closed: 15 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
•