ReleaseEngineering/Archive/Android Tegras: Difference between revisions

disambiguate tegra model & host
(disambiguate tegra model & host)
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. 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 all the Tegras report to test-master01:


http://test-master01.build.mozilla.org:8012/buildslaves?no_builders=1
http://test-master01.build.mozilla.org:8012/buildslaves?no_builders=1
Confirmed users
1,364

edits