Confirmed users
1,905
edits
Auto-tools/Meetings/2012-06-11: Difference between revisions
→Notes
(→Notes) |
|||
| (17 intermediate revisions by 9 users not shown) | |||
| Line 6: | Line 6: | ||
** [wlach] - Added some preliminary support for the Pandaboard to Eideticker ([https://github.com/mozilla/eideticker/commit/7361e4c89a9f48e47ea789c3b9d6da176b47a1c9 commit]), used for testing performance in {{bug|751347}}. | ** [wlach] - Added some preliminary support for the Pandaboard to Eideticker ([https://github.com/mozilla/eideticker/commit/7361e4c89a9f48e47ea789c3b9d6da176b47a1c9 commit]), used for testing performance in {{bug|751347}}. | ||
** [jgriffin] - Turned on mochitest-plain on the B2G continuous-integration system: {{bug|759887}}. Need to investigate some random failures which are causing chunks to fail to start. | ** [jgriffin] - Turned on mochitest-plain on the B2G continuous-integration system: {{bug|759887}}. Need to investigate some random failures which are causing chunks to fail to start. | ||
** [mdas] - Added code to Marionette's perf test framework to post data to Datazilla! | |||
* {{miss| | * {{ok|Provide generic interfaces/web app plugability for new harnesses to reuse the same infrastructure backend}} | ||
** [jeads|carljm|camd] We can now create new datazilla projects in an automated fashion. This includes building an object store and performance database to collect json objects and index them in an RDBS schema. Once a project is created, it can be posted to immediately. This is available for testing on Mozilla-MPT vpn. Contact jeads or carljm if you need to start a project. | |||
* {{miss|Ensure that new UI is based on extensible statistics package that can be used both by developers and the graphserver UI.}} | |||
** [jeads] This goal was deferred in favor of new goal to detect regression per push. This doesn't mean there is no UI for datazilla, there is a "stock" UI available that allows you to examine all data submitted. We stopped extending it in mid April to concentrate on setting up a system that can detect a performance regression in an automated fashion. | |||
* {{ok|Signal From Noise Phase II - Make the same noise-reduction changes we made on Tp5 on all the other page-load tests and ensure all performance tests are sending raw observations to Datazilla.}} | * {{ok|Signal From Noise Phase II - Make the same noise-reduction changes we made on Tp5 on all the other page-load tests and ensure all performance tests are sending raw observations to Datazilla.}} | ||
** [jmaher] - all changes to tests are running side by side on mozilla-central. | ** [jmaher] - all changes to tests are running side by side on mozilla-central. | ||
* {{risk| | * {{risk|Upgrade bugzilla.mozilla.org to Bugzilla version 4.2}} | ||
** [glob] assisted fox2mike in setup of bugzilla.allizom.org | |||
* {{ok|Refactor how rapid-release tracking flags are implemented for improved performance and maintainability}} | |||
* {{ok|Reduce android test automation instability and make it easier for the web QA and desktop QA teams to write and run automated tests.}} | * {{ok|Reduce android test automation instability and make it easier for the web QA and desktop QA teams to write and run automated tests.}} | ||
| Line 24: | Line 30: | ||
=== Mozbase === | === Mozbase === | ||
* [henrik] Released [http:// | * [henrik] Released [http://www.hskupin.info/2012/06/11/mozinstall-1-0-released/ MozInstall v1.0] which includes an uninstaller now | ||
=== Mozmill === | === Mozmill === | ||
| Line 36: | Line 42: | ||
=== Bugzilla === | === Bugzilla === | ||
* june 7th updates: http://globau.wordpress.com/2012/06/07/bmo-push/ | |||
* [dkl+glob] work on the ongoing database cleanup following the failed database consistency correction | |||
* [glob+dkl] misc upstream reviews and patches | |||
* [dkl+glob] bmo administration work | |||
* [glob] blocked extremely broad query from labs which dropped the load across the webhead cluster by 40% | |||
=== Eideticker === | === Eideticker === | ||
| Line 66: | Line 77: | ||
=== Signal From Noise === | === Signal From Noise === | ||
* [jmaher] - final changes to tests are running [[http://people.mozilla.org/~jmaher/sxs/tp5n/sxs.html side by side]] | |||
=== Talos === | === Talos === | ||
* [jhammel] working on making results reporting more extensible and sane (needed for jetperf and talos+mozharness) | * [jhammel] working on making results reporting more extensible and sane (needed for jetperf and talos+mozharness) | ||
* [jmaher] - dromaeo raw results landed (not deployed), will work on xperf raw results | * [jmaher] - dromaeo raw results landed (not deployed), will work on xperf raw results | ||
* [jmaher] - will be working on removing enablePrivilege from talos this week | |||
=== Mobile Automation === | === Mobile Automation === | ||
| Line 77: | Line 90: | ||
=== Marionette === | === Marionette === | ||
* [mdas] finishing up perf test work, will move on to fixing regressions | * [mdas] finishing up perf test work, will move on to fixing regressions | ||
* [jgriffin] - Turned on mochitest-plain on the B2G continuous-integration system: {{bug|759887}}. Need to investigate some random failures which are causing chunks to fail to start. | |||
* [mdas] - Added code to Marionette's perf test framework to post data to Datazilla! | |||
=== Web QA === | === Web QA === | ||
* [dburns] Released Selenium 2.23 | |||
=== Bughunter === | === Bughunter === | ||
| Line 88: | Line 104: | ||
* [carljm] database isolation for datazilla tests | * [carljm] database isolation for datazilla tests | ||
* [carljm] investigated querying hg.mozilla.org for changeset ordering | * [carljm] investigated querying hg.mozilla.org for changeset ordering | ||
* [camd] code work related to implementing the objectstore usage for data input | |||
* [jeads|samliu] Set up mariadb and the TokuDB storage engine for collecting performance data. Transferred ~340,000 json structures, about half of the development talos data as a test. On a qualitative level, mariadb performs substantially faster than MySQL and InnoDB. | |||
* [jeads] Wrote a push walker script to examine t-test results for a child/parent push chain. | |||
* [jeads] Refactored the data ingestion method to make use of MySQL's INSERT … ON DUPLICATE KEY UPDATE strategy. This should reduce load and potential concurrency issues. | |||
=== autophone/Noah's Ark === | === autophone/Noah's Ark === | ||
| Line 110: | Line 130: | ||
* [carljm] put together and presented project proposal/estimate | * [carljm] put together and presented project proposal/estimate | ||
=== Firebug Testing === | |||
* [ahal] updated harness to reflect recent move of Firebug team to git | |||
* [ahal] fixed some bugs and got the client VM's running again: http://getfirebug.com/testresults/?dburi=http://firebug.couchone.com/ | |||
== Upcoming Events == | == Upcoming Events == | ||
| Line 121: | Line 145: | ||
* The list of standing weekly meetings somehow got dropped from recent meeting pages, and is anyway out-of-date. Let's keep it up-to-date! | * The list of standing weekly meetings somehow got dropped from recent meeting pages, and is anyway out-of-date. Let's keep it up-to-date! | ||
* Please remember to submit Q3 goals by EOD Thursday to https://etherpad.mozilla.org/Ateam-Q3-Goals-Submissions | |||
* The new goals section is great, but what about the set of highlights that we used to copy & paste into the wiki for the general meeting. Not everything we do necessarily corresponds to a top priority goal. Should we bring something like that back? | |||
=== Take notes [https://etherpad.mozilla.org/A-TeamMeetingNotes here] and copy and paste them to this section afterwards. === | === Take notes [https://etherpad.mozilla.org/A-TeamMeetingNotes here] and copy and paste them to this section afterwards. === | ||
=== Notes === | === Notes === | ||
* We decided to bring back the '''highlights''' section at the top of the meeting wiki; this will be used to place announcements and other activities that someone wants to highlight. The MC won't need to fill out this section. | |||
=== Holidays and Trips === | === Holidays and Trips === | ||
| Line 132: | Line 162: | ||
=== Next week MC === | === Next week MC === | ||
* mcote is MC next week | |||
* next week's in-depth project discussion will be about MozTrap, led by camd | |||
== Misc == | == Misc == | ||
* | * Sebastien Thrun is offering a free course on statistics late June through Udacity, which might be interesting for some people given our recent focus on more rigorous analysis in various projects (Datazilla, Talos, Eideticker, Peptest, etc.). I (wlach) took Professor Thrun's course on AI last fall and it was great: http://www.udacity.com/overview/Course/st101/CourseRev/1 | ||