EngineeringProductivity/Meetings/2012-02-13: Difference between revisions

Jump to navigation Jump to search
no edit summary
No edit summary
Line 2: Line 2:


* bugzilla
* bugzilla
** [dkl] Implemented AutoLand BMO extension for Lukas Blakk for integrating with Auto Try system (under review)
** [glob] more push work (https://github.com/globau/bugzilla-push)
** [glob] more push work (https://github.com/globau/bugzilla-push)
** [glob] tweaked bmo's memory usage, no longer recompiling perl with each request
** [glob] tweaked bmo's memory usage, no longer recompiling perl with each request
Line 15: Line 16:
** [mdas] added a 'make test' command to make it easier for the b2g guys to start testing with it.
** [mdas] added a 'make test' command to make it easier for the b2g guys to start testing with it.
** [mdas] Added logging, so test users can add their own log messages (https://developer.mozilla.org/en/Marionette/Marionette#Debugging)
** [mdas] Added logging, so test users can add their own log messages (https://developer.mozilla.org/en/Marionette/Marionette#Debugging)
** [jgriffon] Many small bug fixes and improvements to make writing tests and running them easier and more reliable.
** [jgriffon] Worked with QA to write some mozTelephony tests.
** [jgriffon] Security review next Monday.
** [jgriffon] Have a local copy of Jenkins running B2G builds and Marionette tests; will set up a production copy on EC2 next week, then work on re-purposing the existing gitbuilder machine as a Jenkins node that will perform automatic merges from m-c into B2G.
* pulse
** [jgriffon] Work on setting up Nagios monitoring for pulse.
** [jgriffon] Work on developing scripts to automatically identify mis-behaving pulse queues, which historically seem to have been the biggest source of problems.
** [jgriffon] Trying to identify a better way of publishing buildbot messages to pulse that won't break consumers by unpredictable changes.


* fennec ARMv6 ({{bug|697205}})
* fennec ARMv6 ({{bug|697205}})
** no report


* signal from noise
* signal from noise
** [jmaher] starting to get clarity on limitations of how to run tests
** [jmaher] starting to get clarity on limitations of how to run tests
** [jmaher] first side by side staging is done, will reconfig early in the week
** [jmaher] first side by side staging is done, will reconfig early in the week
** [jmaher] lots of churn on cleaning up talos configuration and result parsing
** [jmaher+jhammel] lots of churn on cleaning up talos configuration and result parsing
** [jhammel] Added user configurable data filters to talos (bug 723569). Interim step to moving all data processing out of Talos.


* graphserver
* graphserver
** [jhammel] talked with armen, jeads, and jmaher about plans for graphserver-next. Agreed on some fundamental architecture decisions:
*** We should be sending all data to graphsever
*** There should be a configurable way to apply filters and drill in to the data (jeads is working on the UI)
*** The schema needs to be reworked to both make sense and be more flexible


* mobile automation
* mobile automation
Line 29: Line 45:
** [jmaher] working on updating the foopies (mobile device masters) with updated talos and toolchains
** [jmaher] working on updating the foopies (mobile device masters) with updated talos and toolchains
** [jmaher] will turn on talos robocop tests hopefully next week
** [jmaher] will turn on talos robocop tests hopefully next week
** [jmaher] evaluating panda boards, working on getting builds and installation steps defined
** [jmaher+wlach] evaluating panda boards, working on getting builds and installation steps defined (http://pandaboard.org)
** [mcote] made some much nicer looking graphs (http://10.250.2.223:8100/#/rawfennecstartup)


* Addon compatible by default automation (https://wiki.mozilla.org/Auto-tools/Projects/Compatibile_By_Default_Automation):
* Addon compatible by default automation (https://wiki.mozilla.org/Auto-tools/Projects/Compatibile_By_Default_Automation):
** [wlach] no change


* Eideticker (https://wiki.mozilla.org/Project_Eideticker):
* Eideticker (https://wiki.mozilla.org/Project_Eideticker):
** [wlach] Some more work on Eideticker dashboard but project temporarily on hold while we sort out the issues with the card in mountain view.
** [wlach] Spent time working to make MozRunner work on Android (https://github.com/wlach/mozbase/tree/mozrunner-remote/mozrunner/mozrunner)


* Ateam Services
* Ateam Services
Line 39: Line 59:


* jetperf harness (http://k0s.org/mozilla/hg/jetperf)
* jetperf harness (http://k0s.org/mozilla/hg/jetperf)
** [jhammel] In beta state but good enough for production.
** [jhammel] next steps: adding to buildbot and graphserver (though no concrete work there yet).


* peptest
* peptest
** no report


== Upcoming Events ==  
== Upcoming Events ==  
Confirmed users
241

edits

Navigation menu