Confirmed users
753
edits
Auto-tools/Meetings/2015-01-26: Difference between revisions
Auto-tools/Meetings/2015-01-26 (view source)
Revision as of 00:15, 27 January 2015
, 27 January 2015bug 1107336
(Firefox UI tests updates) |
(bug 1107336) |
||
| (19 intermediate revisions by 12 users not shown) | |||
| Line 1: | Line 1: | ||
= Notices, Highlights, Roundtable = | = Notices, Highlights, Roundtable = | ||
* Significant Contributions | * Significant Contributions | ||
* [jmaher] A-Team [[https://etherpad.mozilla.org/ateam-community-day community day]] - Tommorrow! | |||
** hack a bit on our tasks | |||
** expect to have folks help out with docs/etc. | |||
** the bootcamp | |||
= Newsgroup and Blog Posts = | = Newsgroup and Blog Posts = | ||
* [ahal] http://ahal.ca/blog/2015/new-mercurial-workflow-part-2/ | |||
= Goal Updates = | = Goal Updates = | ||
| Line 17: | Line 23: | ||
* '''progress since last update''': | * '''progress since last update''': | ||
** {{bug|906712}} Largely busy with other tasks, but have incorporated feedback on the api and requested review on the patch. | ** {{bug|906712}} Largely busy with other tasks, but have incorporated feedback on the api and requested review on the patch. | ||
** {{bug|1107336}} - WPTRunner patch created and new try pushes after it landed and was backed out. | |||
=== Support the conversion of targeted P1 mozmill tests to Marionette and get them running in CI [hskupin] === | === Support the conversion of targeted P1 mozmill tests to Marionette and get them running in CI [hskupin] === | ||
| Line 28: | Line 35: | ||
** Barbara started to work on investigating the default preferences for Marionette ({{bug|1123683}}) | ** Barbara started to work on investigating the default preferences for Marionette ({{bug|1123683}}) | ||
** Chris is working on getting the location bar ui module implemented | ** Chris is working on getting the location bar ui module implemented | ||
** Chris is preparing | ** Chris is preparing training materials for the training next week | ||
=== Resolve P1 bugs blocking the release of Marionette 1.0 [AutomatedTester, ato, jgraham] === | === Resolve P1 bugs blocking the release of Marionette 1.0 [AutomatedTester, ato, jgraham] === | ||
| Line 35: | Line 42: | ||
* '''progress since last update''': | * '''progress since last update''': | ||
** [ato] Bug 1107706 is nearly done, but spending much time and frustration on B2G. | ** [ato] Bug 1107706 is nearly done, but spending much time and frustration on B2G. | ||
** [jgraham] Marionette-independent code split out of proxy into its own library, but mostly working on other goals. | |||
** [AutomatedTester] {{Bug|912715}} landed that fixes inconsistency between findElement and findElements | |||
===''Supporting Tasks''=== | ===''Supporting Tasks''=== | ||
| Line 65: | Line 74: | ||
=== Ingest all Talos data with Treeherder and develop a UI that can be used to view current and historical data [wlach] === | === 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. | * 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''': | * '''progress since last update''': Really starting to come together. Initial pull request filed (https://github.com/mozilla/treeherder-ui/pull/289), should be landing pending resolution of mdoglio's requests. Lots of polish / refinement required but we're getting there. Screenshot: http://people.mozilla.org/~wlachance/treeherder-graphs-2014-01-21.png | ||
== Treeherder == | == Treeherder == | ||
| Line 72: | Line 81: | ||
* 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. | * 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}} | * bug: {{bug|1113322}} | ||
* '''progress since last update''': | * '''progress since last update''': {{bug|1097090}} is now under review. No much progress because I have been working on Mozreview last week. | ||
=== Develop a prototype structured log viewer [camd] === | === Develop a prototype structured log viewer [camd] === | ||
| Line 78: | Line 87: | ||
* bug: {{bug|1113873}} | * bug: {{bug|1113873}} | ||
* '''progress since last update''': | * '''progress since last update''': | ||
** Didn't get a chance to work on this in this period. No new progress. | |||
=== Develop a minimal UI that sheriffs can use to file new intermittents [edmorley] === | === Develop a minimal UI that sheriffs can use to file new intermittents [edmorley] === | ||
* details: develop a usable but minimal UI that sheriffs can use to quickly file new intermittent issues; the UI should automatically fill out some of the details that sheriffs normally have to find manually. Future iterations can improve on this by auto-filling more fields. | * details: develop a usable but minimal UI that sheriffs can use to quickly file new intermittent issues; the UI should automatically fill out some of the details that sheriffs normally have to find manually. Future iterations can improve on this by auto-filling more fields. | ||
* bug: {{bug|1117583}} | * bug: {{bug|1117583}} | ||
* '''progress since last update''': | * '''progress since last update''': None - worked on supporting tasks below (and to a much lesser extent, my other personal deliverable). Infra/reliability & other issues still remain that are higher priority than new features. | ||
===''Supporting Tasks''=== | ===''Supporting Tasks''=== | ||
* Continue to improve the performance and operational aspects of the system | * Continue to improve the performance and operational aspects of the system | ||
** Dealt with tree-closing issues due to DB locks | |||
** Fixing the fact that we never used the DB read host (awaiting testing/deployment) | |||
** During the tree closure debugging also discovered jobs could get stuck during ingestion in the 'loading' state, bug filed | |||
** Fixed log parsing exceptions seen on production | |||
** Limited max number of revisions ingested to avoid timeouts with merge day pushes | |||
** Reduced data lifecycle from 5 to 4 months to alleviate shortage of DB disk space & discovered performance artefacts were not being expired (PR ready to land) | |||
* Identify and resolve remaining issues blocking TBPL EOL - treeherder parts: {{bug|1059400}}, other parts: {{bug|1054977}} | * Identify and resolve remaining issues blocking TBPL EOL - treeherder parts: {{bug|1059400}}, other parts: {{bug|1054977}} | ||
** Survey emailed out: [https://groups.google.com/forum/#!topic/mozilla.dev.tree-management/CtkSFWbtAd0 newsgroup post] | |||
** Several developer reported issues fixed (correct timestamp in TBPLbot comments, missing TinderboxPrints, Persona login for emails longer than N characters, reduced target_blank usage, missing bugs suggestions, talos panel for e10s talos, broken "push not processed" refresh, filtering by author on Try) | |||
===''Backlog''=== | ===''Backlog''=== | ||
| Line 104: | Line 122: | ||
* bug: {{bug|1051056}} | * bug: {{bug|1051056}} | ||
* '''progress since last update''': | * '''progress since last update''': | ||
** Made some progress last week after the upstream 5.0rc1 release went out but got called back to do another spin due to a missed error. Hopefully finishing the respin today/tomorrow and then back full time on the goal. Should hopefully have a working prototype by end of week. | |||
=== GitHub authentication [dylan] === | === GitHub authentication [dylan] === | ||
| Line 135: | Line 154: | ||
=== Prototype a retrigger-based bisection tool [armenzg, jmaher] === | === 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: 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. | ||
* Project repo: https://github.com/armenzg/mozilla_ci_tools | |||
* '''progress since last update''': | * '''progress since last update''': | ||
** I've done the first release of the library that allows us to trigger jobs in automation. | ** I've done the first release of the library that allows us to trigger jobs in automation. | ||
| Line 207: | Line 227: | ||
== Community == | == Community == | ||
=== Increase 'contributor friendliness' of our projects [jmaher, all] === | |||
* 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 | * 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''': | * '''progress since last update''': | ||
| Line 231: | Line 251: | ||
= Holidays and Trips = | = Holidays and Trips = | ||
* [mcote] on PTO starting Jan 28. Back Feb 8. | |||
= Misc = | = Misc = | ||