Confirmed users, Bureaucrats and Sysops emeriti
1,009
edits
Firefox/Meeting/17-Sep-2013: Difference between revisions
Jump to navigation
Jump to search
Firefox/Meeting/17-Sep-2013 (view source)
Revision as of 16:25, 17 September 2013
, 17 September 2013→Australis
| Line 17: | Line 17: | ||
* We've backfilled the TART performance data for Windows XP going back to about mid-April, and dumped it into Datazilla (thanks jmaher!). | * We've backfilled the TART performance data for Windows XP going back to about mid-April, and dumped it into Datazilla (thanks jmaher!). | ||
** [https://datazilla.mozilla.org/?start=1374858213&stop=1379431813&product=Firefox&repository=Firefox&os=win&os_version=5.1.2600&test=tart&compare_product=Firefox&compare_repository=UX&project=talos The graphs paint a pretty interesting tale.] Green is m-c, purple is UX. Each graph that you're looking at is one of the subtests for TART. These graphs just came in, so we're still verifying their accuracy. | ** [https://datazilla.mozilla.org/?start=1374858213&stop=1379431813&product=Firefox&repository=Firefox&os=win&os_version=5.1.2600&test=tart&compare_product=Firefox&compare_repository=UX&project=talos The graphs paint a pretty interesting tale.] Green is m-c, purple is UX. Each graph that you're looking at is one of the subtests for TART. These graphs just came in, so we're still verifying their accuracy. | ||
* We've identified a m-c merge changeset that caused a regression across the board for UX, but didn't seem to affect m-c. See {{bug|916859}}. Now the challenge is to determine *which* changeset in that merge caused the problem. Mike is going to chat with graphics and layout to see if they can point out any obvious culprits to try backing out. Failing that, manual bisection - which is going to be a real trick, since | * We've identified a m-c merge changeset that caused a regression across the board for UX, but didn't seem to affect m-c. See {{bug|916859}}. Now the challenge is to determine *which* changeset in that merge caused the problem. Mike is going to chat with graphics and layout to see if they can point out any obvious culprits to try backing out. Failing that, manual bisection - which is going to be a real trick, since we'll need to merge from UX every time. | ||
===Downloads API=== | ===Downloads API=== | ||