Closed
Bug 821007
Opened 12 years ago
Closed 11 years ago
mozmill should log request/response bodies of update requests
Categories
(Mozilla QA Graveyard :: Mozmill Tests, defect, P2)
Mozilla QA Graveyard
Mozmill Tests
Tracking
(Not tracked)
RESOLVED
WONTFIX
People
(Reporter: bhearsum, Assigned: AndreeaMatei)
References
()
Details
(Whiteboard: s=130211 u=enhance c=update p=1)
Spawned out of bug 817688, comment #27. Not sure how to do this exactly, but it would be extremely helpful when diagnosing update problems that could be server related.
Comment 1•12 years ago
|
||
Not specifically a mozmill issue but more software update test related. Which connection we would have to log specifically. I ask because we can't log anything which would blow up the log drastically.
Component: Mozmill → Mozmill Tests
Product: Testing → Mozilla QA
Reporter | ||
Comment 2•12 years ago
|
||
(In reply to Henrik Skupin (:whimboo) from comment #1) > Not specifically a mozmill issue but more software update test related. > Which connection we would have to log specifically. I ask because we can't > log anything which would blow up the log drastically. Huge logs is better than logs that don't have enough info. I don't think we should block this on special hooks in the updater code.
Comment 3•12 years ago
|
||
So we could observe 'http-on-examine-response' by setting the observer before checking for updates and disable it right after the update has been downloaded. The additional information shouldn't be that much in this case. Not sure yet if we should add it to the report or the console log only. Ben, what's your take on that proposal? Does it sound ok?
Priority: -- → P2
Comment 4•12 years ago
|
||
See also https://developer.mozilla.org/en/HTTP_Logging. DNS logging would be useful to identify the CDN being used, if it provides the IP address that download.cdn.mozilla.net resolves to.
Reporter | ||
Comment 5•12 years ago
|
||
(In reply to Henrik Skupin (:whimboo) from comment #3) > So we could observe 'http-on-examine-response' by setting the observer > before checking for updates and disable it right after the update has been > downloaded. The additional information shouldn't be that much in this case. > Not sure yet if we should add it to the report or the console log only. > > Ben, what's your take on that proposal? Does it sound ok? I don't fully understand, what that means, but if gets us full requests and responses, sounds great!
Updated•11 years ago
|
Whiteboard: s=130211 u=enhance c=update p=1
Assignee | ||
Updated•11 years ago
|
Assignee: nobody → andreea.matei
Status: NEW → ASSIGNED
Comment 6•11 years ago
|
||
Andreea, can we please get an update? This sprint entry is waiting for 2 months now!
Assignee | ||
Comment 7•11 years ago
|
||
Sorry for that, I have focused on P1 bugs and other P2 that were failures mainly, above this that is an enhancement. Also now I'm working with Daniela on the software update issue for Windows 8. I will start on it today, maybe get some more clarity over Ask an Expert meeting regarding the steps here and have a patch ready soon.
Assignee | ||
Comment 8•11 years ago
|
||
We have decided to go with HTTP log as Nick Thomas suggested, filed the issue under mozmill-ci for that, you can find it here: https://github.com/mozilla/mozmill-ci/issues/229
Status: ASSIGNED → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
Assignee | ||
Updated•11 years ago
|
Resolution: FIXED → WONTFIX
Updated•5 years ago
|
Product: Mozilla QA → Mozilla QA Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•