Auto-tools/Meetings/2015-01-12: Difference between revisions

← Older edit

Auto-tools/Meetings/2015-01-12 (view source)

Revision as of 17:05, 13 January 2015

2,965 bytes added , 13 January 2015

Add bug

Armenzg

Confirmed users

3,990

edits

@@ Line 4: / Line 4: @@
 * jgriffin: re-introductions - Henrik
 * jgriffin: Q1 goal updates
+* jgriffin: Q4 goal debrief
+* A-Team Community Day - January 27th!
 = Newsgroup and Blog Posts =
@@ Line 22: / Line 24: @@
 * '''progress since last update''':
 ** alert/confirm/prompt implementation ({{bug|906712}}) f?
+** {{bug|1107336}} dependent up for review. See {{bug|1118201}}. Work on {{bug|1107336}} complete and will put up for review if there are no changes required to dependent.
 === Support the conversion of targeted P1 mozmill tests to Marionette and get them running in CI [hskupin] ===
@@ Line 28: / Line 31: @@
 * stretch goal: support the conversion of Search tests
 * '''progress since last update''':
+** Waiting for next marionette-client release ({{bug|1120364}}) to continue with window and tab handling support
+** Finished [https://github.com/mozilla/firefox-greenlight-tests/pull/40 prefs module] and added [https://github.com/mozilla/firefox-greenlight-tests/pull/42/ Travis support]
+** [https://github.com/mozilla/firefox-greenlight-tests/issues/44 Discussion] about how to name the repository - my proposal would be 'Firefox UI Tests"
 === Resolve P1 bugs blocking the release of Marionette 1.0 [AutomatedTester, ato, jgraham] ===
@@ Line 33: / Line 39: @@
 * stretch goal: release Marionette 1.0
 * '''progress since last update''':
+** {{bug|1090925}} has been for Feedback
+** Very-rough version of WebDriver <-> Marionette proxy working based on a guess of what the spec might look like.
+*** Next step: work out how to launch Firefox for a session when required.
 ===''Supporting Tasks''===
@@ Line 47: / Line 56: @@
 === Better Bugzilla integration with MozReview [dkl] ===
 * details: Make MozReview data in Bugzilla more useful by creating a Bugzilla field that contains dynamic information about a MozReview review request
-* '''progress since last update''':
+* '''progress since last update''': None, finishing up on 5.0 upstream Bugzilla release.
 ===''Supporting Tasks''===
 * continue improvements to the multi-commit UI
+** '''progress since last update''':
+*** mconley posted a new [https://reviewboard.mozilla.org/r/661/ review request] for {{bug|1064111}} ('Move contents of "Commits" tab in rbmozui to the main review request page')
 == Perfherder ==
@@ Line 56: / Line 67: @@
 === Ingest all Talos data with Treeherder and develop a UI that can be used to view current and historical data [wlach] ===
 * details: We want to use Treeherder to store and display Talos performance data, because Datazilla is being deprecated and Graphserver doesn't support the kind of performance analysis we'd like to perform on the data.
 * '''progress since last update''':
+** Data: All data seems to be in treeherder. Waiting for ekyle to stand up a new instance of dzAlerts using treeherder data so we can validate that the same alerts are generated. Likely no progress this week as he's on vacation.
+** UI: Tracking progress on Trello here: https://trello.com/b/PQSxEIZf/perfherder-ui-tasks
+*** New since last time: Fixed some nits from mdoglio and jfrench, allowed deleting series, style tweaks.
 == Treeherder ==
@@ Line 63: / Line 77: @@
 * details: Tier 1 and Tier 2 jobs will have different sheriffing guidelines and different expectations.  Accordingly, we need to display them and allow users to interact with them differently.
 * bug: {{bug|1113322}}
-* '''progress since last update''': not started yet. preparing the ground as part of bug 1097090
+* '''progress since last update''': not started yet. preparing the ground as part of {{bug|1097090}}
 === Develop a prototype structured log viewer [camd] ===
@@ Line 97: / Line 111: @@
 === Implement versioning framework for REST API [dkl] ===
-* '''progress since last update''':
+* '''progress since last update''': Design work completed. Will work on implementation soon right after finishing with upstream 5.0 Bugzilla release.
 === GitHub authentication [dylan] ===
-* '''progress since last update''':
+* '''progress since last update''': Plan/design ready, implementation delayed by previous quarter's goals (guided bug entry).
 == DevTools Harness ==
@@ Line 106: / Line 120: @@
 === Get the DevTools harness running in continuous integration [ted] ===
 * details: Take the prototype that was developed in 2014 Q4 (https://github.com/luser/luciddream) and get it running in continuous integration and visible in Treeherder. It's TBD whether this will be run in buildbot or TaskCluster, but we should get it running somewhere per-commit this quarter against linux desktop Firefox and a B2G emulator.
-* '''progress since last update''':
+* '''progress since last update''': Nothing to report, working on other tasks and catching up from holiday backlog. Planning to chat about status of Taskcluster this week to decide on feasibility of using it.
 == CloudServices Automation ==
@@ Line 116: / Line 130: @@
 === Prototype a retrigger-based bisection tool [armenzg, jmaher] ===
-* details: Create a prototype of a command-line tool that can be used by sheriffs and others to automate retrigger-based bisection.  This could be used to help bisect new intermittent oranges, and to backfill jobs that have been skipped due to coalescing.  Integration with Treeherder or other service will be done later.
+* details: {{bug|1120990}} - Create a prototype of a command-line tool that can be used by sheriffs and others to automate retrigger-based bisection.  This could be used to help bisect new intermittent oranges, and to backfill jobs that have been skipped due to coalescing.  Integration with Treeherder or other service will be done later.
-* '''progress since last update''':
+* '''progress since last update''': Nothing new; a lot of catch up after the holiday break
 ===  Store high-resolution testcase data ("ActiveData") [ekyle, ahal] ===
 * details: Create a Proof of Concept “big data” project which will store information about every test file we run:  test status, error details, test machine and test duration to begin with.  We will use this project to develop schemas and queries that work with data this large, and we will use this data to normalize chunk sizes and provide details about which tests never fail.
 * '''progress since last update''':
+** [ahal] Set up aws instance that listens to pulse and both sends jobs over rq to be processed by workers and stores them in mongodb for historical reprocessing
+** [ahal] Set up supervisord dashboard for managing various processes
 ===  Implement the ability to normalize chunk durations in mochitest [ahal] ===
@@ Line 128: / Line 144: @@
 * bug: {{bug|1054247}}
 * '''progress since last update''':
+** [ahal] None besides initial brainstorming/planning, working on ActiveData project
 === Create Android 4.4 emulator image for automated tests [gbrown] ===
@@ Line 137: / Line 154: @@
 ** "greening" of tests
 * '''progress since last update''':
+** created an avd from the Android 4.4 sdk
+** built custom images from AOSP
+** testing both locally
 === Help Releng reduce test load [jmaher] ===
 * details: This quarter, we’ll validate the data from SETA and provide some recommendations to Releng about which jobs/platforms we could schedule less often in order to reduce test load.  We’ll monitor the impact of these changes in terms of sheriffing burden and the number of retriggers this demands, and may adjust as needed.  In subsequent quarters, we’ll use additional data from the high-resolution testcase data project and OrangeFactor to provide more finely-tuned scheduling changes.
 * '''progress since last update''':
+** reducing useless talos jobs - turned off talos on b2g*, esr* branches; this week reducing half of the talos tests on osx 10.6
+** SETA - cleaned up code- updating from treeherder - ETA this week to have SETA producing daily reports.
+** next steps: work with sheriffs and releng to have a plan for disabling tests
 ===''Supporting Tasks''===
@@ Line 156: / Line 179: @@
 * details: We want to expand the pool of people who can perform performance sheriffing to make it scale better, and to reduce the bus factor problem.
 * '''progress since last update''':
+** identified one candidate for sheriffing - have given preliminary information, will know next week if this sticks.
 ===''Supporting Tasks''===
@@ Line 172: / Line 196: @@
 * details: Ensure that all ongoing projects have a friendliness rating of at least 6, as shown on https://wiki.mozilla.org/Auto-tools/Projects/Everything
 * '''progress since last update''':
+** no progress - working on talos, seta, and runbydir
 ===''Supporting Tasks''===