Closed
Bug 569477
Opened 15 years ago
Closed 14 years ago
If updates are served via a slow mirror the failure should include the mirror address
Categories
(Mozilla QA Graveyard :: Mozmill Tests, defect, P1)
Mozilla QA Graveyard
Mozmill Tests
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: whimboo, Assigned: whimboo)
References
()
Details
(Whiteboard: [release-process-improvement][fixed by bug 604370])
Randomly we see failures in our update checks like that one:
http://brasstacks.mozilla.com/couchdb/mozmill/_design/reports/_show/report/290c43ba6dc411dfb9b3005056a533eb
The reason is that we do not finish the download process within the 6 minute time schedule. The reason should be slow mirrors we are downloading from. Right now we do not have any information about those in our failure report. Would be a good idea to include the download URL so we can report those issues to releng.
Assignee | ||
Comment 1•15 years ago
|
||
Robert, is there an easy way for me from the Mozmill side to check from which mirror we are downloading the update? Something like a property I can read? If not, what else would have to be done? Thanks.
Comment 2•15 years ago
|
||
it is routed to whatever server dns returned... don't know of anything that can reasonably be done about to get that info. Perhaps ask one of the necko people
Assignee | ||
Comment 3•15 years ago
|
||
Thanks Rob. I also talked with Christian Biesinger and he mentioned that there is probably only one possible solution available at the moment. We would have to use the observer for NS_HTTP_ON_EXAMINE_RESPONSE_TOPIC:
http://mxr.mozilla.org/mozilla-central/source/netwerk/protocol/http/public/nsIHttpProtocolHandler.idl#156
Lets see if I can get that to work. If it will not give us the correct information we will have to mark this bug as WONTFIX.
Assignee | ||
Updated•14 years ago
|
Component: Application Update → Mozmill Tests
Product: Toolkit → Testing
QA Contact: application.update → mozmilltests
Whiteboard: [release-process-improvement]
Assignee | ||
Updated•14 years ago
|
Priority: -- → P2
Assignee | ||
Comment 5•14 years ago
|
||
With todays build the fix for bug 597664 will give us a new attribute for the final URL we can use. That makes the implementation much easier.
Depends on: 597664
Assignee | ||
Comment 6•14 years ago
|
||
This will be fixed with my work on bug 604370.
Depends on: 604370
Priority: P2 → P1
Assignee | ||
Updated•14 years ago
|
Whiteboard: [release-process-improvement] → [release-process-improvement][will be fixed by bug 604370]
Assignee | ||
Updated•14 years ago
|
Summary: [mozmill] If updates are served via a slow mirror the failure should include the mirror address → If updates are served via a slow mirror the failure should include the mirror address
I assume by duping bug 597664 you plan to implement blacklisting on this bug? Just logging the URL will not achieve what is proposed in bug 597664. It's not enough to just log the URL, we need to do something with that URL once it is logged.
Assignee | ||
Comment 8•14 years ago
|
||
(In reply to comment #7)
> I assume by duping bug 597664 you plan to implement blacklisting on this bug?
You probably meant bug 597664. And no, we can't do blacklisting on our side. That's the job of releng. See my comment on that other bug.
Assignee | ||
Comment 9•14 years ago
|
||
Because not all slower mirrors will cause a timeout, I have filed bug 607800 to also track the download duration and patch size.
Assignee | ||
Updated•14 years ago
|
Assignee: nobody → hskupin
Status: NEW → ASSIGNED
Assignee | ||
Comment 10•14 years ago
|
||
Move of Mozmill Test related project bugs to newly created components. You can
filter out those emails by using "Mozmill-Tests-to-MozillaQA" as criteria.
Product: Testing → Mozilla QA
Version: Trunk → unspecified
Assignee | ||
Comment 11•14 years ago
|
||
Fixed as part of my patch on bug 604370. Please keep in mind that it will only work on trunk right now, because we are still waiting for backports of bug 597664.
Status: ASSIGNED → RESOLVED
Closed: 14 years ago
Resolution: --- → FIXED
Whiteboard: [release-process-improvement][will be fixed by bug 604370] → [release-process-improvement][fixed by bug 604370]
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
•