ReleaseEngineering/Archive/Android Tegras: Difference between revisions

Jump to navigation Jump to search
document new tegra -> foopy -> build master mapping
(disambiguate tegra model & host)
(document new tegra -> foopy -> build master mapping)
Line 108: Line 108:
If you see a Tegra that has been running for 4+ hours, then it most likely has a hung fennec process. There will be a matching server.js daemon on the foopy.
If you see a Tegra that has been running for 4+ hours, then it most likely has a hung fennec process. There will be a matching server.js daemon on the foopy.


The easiest way to find Tegras that are in this state is via the buildbot-master. ''(N.B. in buildbot reports, all tegras report their [https://en.wikipedia.org/wiki/Nvidia_Tegra#Tegra_2_series model #], e.g. "Tegra 250". Do not confuse model name with a tegra host name, e.g. <tt>tegra-250</tt>.)'' Currently all the Tegras report to test-master01:
The easiest way to find Tegras that are in this state is via the buildbot-master. ''(N.B. in buildbot reports, all tegras report their [https://en.wikipedia.org/wiki/Nvidia_Tegra#Tegra_2_series model #], e.g. "Tegra 250". Do not confuse model name with a tegra host name, e.g. <tt>tegra-250</tt>.)''. Currently (2011-12-20) all tegras on a foopy use the same build master:


http://test-master01.build.mozilla.org:8012/buildslaves?no_builders=1
{| border="1" cellpadding="2"
!foopy #!!Master URL
|-
| <18
| [http://test-master01.build.mozilla.org:8012/buildslaves?no_builders=1 test-master01]
|-
| >=18 & even
| [http://buildbot-master20.build.mozilla.org:8201/buildslaves?no_builders=1 buildbot-master20]
|-
| >18 & odd
| [http://buildbot-master19.build.mozilla.org:8201/buildslaves?no_builders=1 buildbot-master19]
|}


Look for Tegras that have a "Last heard from" of >4 hours. If the list of "Recent builds" for the Tegra are flapping between exceptions/failures/warnings, i.e. the status is all sorts of different pretty colours, that's a good sign that there's a stray fennec process fouling things up.
Look for Tegras that have a "Last heard from" of >4 hours. If the list of "Recent builds" for the Tegra are flapping between exceptions/failures/warnings, i.e. the status is all sorts of different pretty colours, that's a good sign that there's a stray fennec process fouling things up.
Confirmed users
1,351

edits

Navigation menu