Closed Bug 908700 Opened 11 years ago Closed 8 years ago

Make sure mozAfterPaint is used correctly within talos

Categories

(Testing :: Talos, defect)

x86_64
Windows 7
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 1254628

People

(Reporter: avih, Unassigned)

References

Details

AFAIK, using mozAfterPaint in talos is sort of a generic cure for cases where the first content paint comes (a while?) after the load event, so it represents the page-load time better as far as the user is concerned.

However, This doesn't necessarily apply to all talos tests, and especially not for tests which gather their own data points and then report an aggregation to talos.

This bug is about going over all talos tests, figure out which ones could benefit from mozAfterPaint, and make sure it's only used where it helps, maybe including changes to talos itself to allow higher-resolution usage of this flag (e.g. I think tsvg/x only needs it at some of the sub-tests).
it sounds like we are revisiting this bug right now in bug 1027481.  Should we dup this bug?
Flags: needinfo?(avihpit)
No, just depend.

This bug is for going over all tests, while bug 1027481 is for one of them. We can continue "phase 2" of bug 1027481 here, because I forgot this bug exists :) Thanks for findind it.
Depends on: 1027481
Flags: needinfo?(avihpit)
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.