Closed
Bug 930439
Opened 11 years ago
Closed 11 years ago
tp5o shutdown has incorrect value due to seconds vs milliseconds
Categories
(Testing :: Talos, defect)
Testing
Talos
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: jmaher, Assigned: jmaher)
References
Details
Attachments
(1 file)
(deleted),
patch
|
wlach
:
review+
|
Details | Diff | Splinter Review |
a fallout from 923770 where the endtimestamp is in python time.time() format and not in javscript time format.
Assignee | ||
Comment 1•11 years ago
|
||
Assignee | ||
Comment 2•11 years ago
|
||
Comment on attachment 821591 [details] [diff] [review] time.time() * 1000 (1.0) unfortunately I see a 500ms regression on ts_paint with this patch, but I don't know how to make the timestamp prior to launching any closer to the actual lauching with mozprocess. nevertheless, this fixes a regression in tp5o0 - shutdown.
Attachment #821591 -
Flags: review?(jhammel) → review?(wlachance)
Comment 3•11 years ago
|
||
Comment on attachment 821591 [details] [diff] [review] time.time() * 1000 (1.0) Review of attachment 821591 [details] [diff] [review]: ----------------------------------------------------------------- Without having investigated the details of why we need the timestamps to be in milliseconds, this looks fine to me. Moving the calculation of the initial timestamp closer to the launching of the process also sounds good, though I worry there's some other problem there that we're not addressing here. Still, looks good to go in. Can always sort out other problems or the real issue some other way. ::: talos/ttest.py @@ +370,4 @@ > setup.run() > setup.wait() > > + env = os.environ.copy() I don't see why this deserves its own line/variable :)
Attachment #821591 -
Flags: review?(wlachance) → review+
Assignee | ||
Comment 4•11 years ago
|
||
pushed and moved the env into the arg list instead of a new line: https://hg.mozilla.org/build/talos/rev/cc936fa80fd8
Assignee | ||
Updated•11 years ago
|
Status: ASSIGNED → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•