Closed
Bug 636534
Opened 14 years ago
Closed 14 years ago
support incremental log output from remote testing harnesses
Categories
(Testing :: General, defect)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: jmaher, Assigned: jmaher)
References
Details
(Whiteboard: [mobile_unittests])
Attachments
(1 file)
2.61 KB,
patch
|
cmtalbert
:
review+
|
Details | Diff | Splinter Review |
currently the mochitest and reftest harness are a fire and wait until 100% done (or timeout). This isn't good for debugging or for buildbot scripts that can monitor for output.
Assignee | ||
Updated•14 years ago
|
Whiteboard: [mobile_unittests]
Assignee | ||
Comment 1•14 years ago
|
||
This patch takes the existing framework for tracking a log file and while we poll for the process being alive or terminated we output any new information from the log file to the host. It is sort of hacky in the sense that every 5 seconds we poll the process (existing code) and transfer the full content of the remote log file while only displaying what is new. Not ideal for large log files, but we run things in such small chunks I don't see this as being a big nightmare.
Assignee: nobody → jmaher
Attachment #514980 -
Flags: review?(ctalbert)
Comment on attachment 514980 [details] [diff] [review]
incrementally pull the remote log file and output to host (1.0)
I think this looks good. As noted it's not going to work efficiently for large files, but I'd like to take this now and work in large file support by doing a "readFromFileOffset" in the agent rather than doing something hacky on the controller side.
Attachment #514980 -
Flags: review?(ctalbert) → review+
Filed bug 636836 to track changing the agent in order to solve this long term.
Assignee | ||
Comment 4•14 years ago
|
||
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → FIXED
Updated•7 years ago
|
Component: New Frameworks → General
You need to log in
before you can comment on or make changes to this bug.
Description
•