EngineeringProductivity/Team Roster/jmaher

From MozillaWiki
Jump to: navigation, search

Personal Status (Updated June 11th, 2012)

A rough list of projects I am currently working on in some form of a priority order

Actions I need to take

  • remote talos logcat
    • proof of concept is done, need to test on try, then come up with a good solution (failed on try due to 'error' string in logcat, working on fix)
  • tegra reconnect logic
    • send Callek some patches to try out
    • look at integrating into existing harnesses
  • enablePrivilege stuff
    • reftest: jsreftest/crashtest: working on patch to do this. Will run on try server tonight. 1 failed test case, but everything else is looking good.
  • amazon cloud testing
    • talk to catlee about gaining access
    • verify tests run, point to orange factor
    • run a few hundred tests, etc...
    • look for stability, run times, ~random oranges
  • bug 763482 - powermeter automation (https://wiki.mozilla.org/Mobile/PowerUsage)
    • work with :mcote on integration into auto-phone
    • rebuild this so installation and launching will run with proper configuration
      • read a configuration file from the disk
    • figure out how to get it to read a config file for power profile, what to log and where to log
    • figure out how to stop the test (send a signal, kill the app)? If we do this will it have a complete log
    • ideally we could log to a file every 10 seconds (or so), so we could just kill the process and uninstall when we are done.
  • work on android top failures (first connect, reftest timeout) and possible solutions (watcher, memory)
  • generate raw results for page centric data
    • need to deploy a new talos with these changes and monitor it for a day or two.
    • work on tbpl bits to turn talos orange
    • leaktests -> datazilla
  • https://etherpad.mozilla.org/rxdroid
    • I need to mock up install/uninstall
    • todo: make base class support NOT_IMPLEMENTED
    • todo: use logging or similar module (caveat, no global variables)
    • verification of a program installation
    • verification of permissions on the filesystem
    • define settings we care about other than resolution if any
    • cleaning up settings and filesystem (rm /mnt/sdcard/tests)
    • formatting filesystem?
    • verifying root access to the device
    • collecting adb logcat information
  • powerball reftests
    • work with AutomatedTester to get a quest posted
    • figure out criteria for comparing
  • look into 'uss' for tp4mobile
    • could get it from procrank
  • mozbase patches from ctalbert, don't want to lose these
  • run talos tests on python2.7 and python2.4 for 5 runs each, verify numbers are similar.
    • work with wlach to get the python 2.7 runs going on our staging environment.

`

in the waiting queue

  • row major for tests, 25 cycles, row major, drop 5 keep 20, tp5n, etc...
  • bug 761125 - android-failures.json
    • 2 bugs filed to investigate the long running tests
    • bug 765248 - need to split into 10 chunks.
  • pandaboard automation
    • need to resolve mac address, reboot, packaging, PXE boot, resolution, graphics performance (per wlach)
  • tp5.1