1494308 - Timestamps don't match reality when running wpt

Status: RESOLVED FIXED

(Testing :: web-platform-tests, enhancement)

Description

[Boris Zbarsky [:bzbarsky]]

My output from mach wpt looks like this:

 0:00.00 INFO Skipping manifest download because existing file is recent
 0:00.00 INFO Updating manifests
 0:05.61 INFO Using 1 client processes
 0:05.73 INFO Starting http server on 127.0.0.1:8000
 0:05.73 INFO Starting http server on 127.0.0.1:8001
 0:05.75 INFO Starting https server on 127.0.0.1:8443 

but the "Updating manifests" step actually took close to a minute of wall-clock time.  So something is off about the timestamps here.

James thinks this has to do with the logger the manifest download uses.

Comment 1

[James Graham [:jgraham]]

Attachment: Bug 1494308 - Use consistent logger in wpt commands

Before we were using a different logger for the manifest download and the actual test run.
This caused timestamps to get reset in a confusing way. Now create the logger early and
share it for all the subseteps.

Depends on D7171

Comment 2

[Andreas Tolfsen ❲:ato❳]

Comment on attachment 9012869 [details]
Bug 1494308 - Use consistent logger in wpt commands

Andreas Tolfsen ❲:ato❳ has approved the revision.

Comment 3

[Pulsebot]

Pushed by [e-mail]:
https://hg.mozilla.org/integration/autoland/rev/ace8fc8c112e
Use consistent logger in wpt commands r=ato

Comment 4

[Cristina Coroiu [:ccoroiu]]

https://hg.mozilla.org/mozilla-central/rev/ace8fc8c112e