Buildbot/Talos/Tests: Difference between revisions

→‎xperf: Clarify that it currently tests startup I/O regressions only
(→‎xperf: Clarify that it currently tests startup I/O regressions only)
Line 442: Line 442:
* contact: :taras, :aklotz, :jmaher
* contact: :taras, :aklotz, :jmaher
* source: [[http://hg.mozilla.org/build/talos/file/tip/talos/xtalos xperf instrumentation]]
* source: [[http://hg.mozilla.org/build/talos/file/tip/talos/xtalos xperf instrumentation]]
* type: Pageloader (tp5n)
* type: Pageloader (tp5n) / Startup
* measuring: IO counters from windows
* measuring: IO counters from windows (currently, only startup IO is in scope)
* reporting: Summary of read/write counters for disk, network (lower is better)
* reporting: Summary of read/write counters for disk, network (lower is better)


Line 453: Line 453:
  * TEST-UNEXPECTED-FAIL : xperf: File 'c:\$logfile' was accessed and we were not expecting it. DiskReadCount: 0, DiskWriteCount: 2, DiskReadBytes: 0, DiskWriteBytes: 32768  
  * TEST-UNEXPECTED-FAIL : xperf: File 'c:\$logfile' was accessed and we were not expecting it. DiskReadCount: 0, DiskWriteCount: 2, DiskReadBytes: 0, DiskWriteBytes: 32768  


In the case that these files are expected to be accessed by your changeset, then we can add them to the [[https://bugzilla.mozilla.org/enter_bug.cgi?product=Testing&component=Talos whitelist]].
In the case that these files are expected to be accessed during startup by your changeset, then we can add them to the [[https://bugzilla.mozilla.org/enter_bug.cgi?product=Testing&component=Talos whitelist]].


Xperf runs tp5 while collecting xperf metrics for disk IO and network IO.  The providers we listen for are:
Xperf runs tp5 while collecting xperf metrics for disk IO and network IO.  The providers we listen for are:
Confirmed users
183

edits