Previous Action Items

• [jmaher/jhammel] - https://bugzilla.mozilla.org/show_bug.cgi?id=787143
  • DONE
• jmaher - follow up on dev.platform post
  • DONE
• jmaher/christina - discuss other tests/data and applying stats to similar tests
  • DONE
• all - figure out a blog posting schedule and who will be posting what/when
• christina - blog and brown bag about all the science behind it title 'she blinded me with science'
• mozregression tool for developers to bisect when a regression happened (as per taras talos meeting)

Datazilla

• [camd] Landed data-check branch

Regression/Improvement Auto Detection

• after reviewing svg* and tdhtml with metrics, it appears we should be able to apply the exact same calculations as we are for tp5n.
  •  :jeads has confirmed that they are doing this by default for all the data, will have data when we update production

Talos (code, deployment)

• updated [wiki] with up to date tests
  • NOTE: this needs to be done quite regularly as we continue to change tests.

• need to add talos commands to mach (i.e. 'mach talos dromaeojs')

Tests

• bug 731159 - tresize live
• bug 770317 - xperf tp5n live - just needs a reconfig (eta tomorrow) to post to graph server

• tp5n for windows with accessibility turned on
• possibly more updates to a11y tests this quarter
• bug 770718 - possibly websockets tests (connections/sec, MB/sec, packets/second) this quarter, including using stoneridge. Estimate a week of work to do this, P2 for now
• tdhml needs an overhaul, low priority

Round Table

• How should we tell developers (now) to hunt for regressions?
  • there are three solutions: compare-talos, compare.py, and https://bugzilla.mozilla.org/show_bug.cgi?id=786504
  • see Action Items below

Action Items

• [jhammel] write bugs for
  • script for running talos locally to detect regressions identically to the manner done via graphserver
  • script for running talos via e.g. try + etc identically to the manner done via graphserver