Search completed in 1.12 seconds.
8 results for "Talos":
Continuous Integration
talos performance tests all performance tests displayed in treeherder are run using the
talos framework, and denoted by the letter t.
...
talos is used to execute several suites for desktop firefox and firefox for android; these suites are denoted using lower-case letters, e.g., t(c d g1 o s tp).
... the
talos indicators in treeherder appear green if the job successfully completed; to see the performance data generated by the jobs, click on the performance tab of the job details panel that pops up when you click on a job in treeherder.
...And 3 more matches
Gecko Profiler FAQ
probably by using
talos, especially if you want to measure and not profile.
... you can make your own
talos pageload test which has just the one page that you’re interested in in its manifest.
Profiling with the Gecko Profiler and Local Symbols on Windows
profiling local
talos runs if you would like to use the gecko profiler with a local
talos run of a local build of firefox for windows, you will need to point
talos to a zipfile containing breakpad-style symbols for your build.
... generate the breakpad symbol files by running ./mach buildsymbols: https://developer.mozilla.org/en/building_firefox_with_debug_symbols#breakpad_symbol_files this will have created symbols under $objdir/dist/ , named after the binary name, architecture and version, so something like "firefox-40.0a1.en-us-win32.crashreporter-symbols.zip" point
talos to this zipfile by passing its path to the --symbolspath flag.
How test harnesses work
(manifestdestiny) potentially sets up an http server for test data (mozhttpd) invokes the binary (mozrunner) it is the job of the shim extension to shut down the browser logging (mozlog, in theory) (run tests, accrue results) cleanup: shutdown the browser check for crashes (mozcrash) reporting (moztest) marionette tests list of testing extensions pageloader (
talos) mochitest: //github.com/realityripple/uxp/blob/master/testing/mochitest/install.rdf (mochitest) ...
Automated performance testing and sheriffing
current list of automated systems we are tracking (at least to some degree):
talos: the main performance system, run on virtually every check-in to an integration branch build metrics: a grab bag of performance metrics generated by the build system arewefastyet: a generic javascript and web benchmarking system areweslimyet: a memory benchmarking tool ...
TPS Tests
it's name stands for testing and profiling tool for sync (which is a misnomer, since it doesn't do any profiling), and it should not be confused with the similarly named tests in
talos.
Mozilla Projects
it's name stands for testing and profiling tool for sync (which is a misnomer, since it doesn't do any profiling), and it should not be confused with the similarly named tests in
talos.