Closed Bug 1174585 Opened 10 years ago Closed 10 years ago

[MTBF] W/SocketClient( 198): write error (Broken pipe)

Categories

(Firefox OS Graveyard :: Stability, defect)

Product:
Firefox OS Graveyard
Component:
Stability
Platform:
ARM
Gonk (Firefox OS)
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(tracking-b2g:+)

Status:
RESOLVED WORKSFORME
Project Flags:
tracking-b2g +

People

(Reporter: wachen, Unassigned)

References

Details

http://mtbf-1:8080/job/flamekk.v2.2.moztwlab01.319.mtbf_op/label=moztwlab-01/384/console STR: 1. running MTBF operationg with extra power 2. after 25 hours, it stucked there with the following message: 14:32:33 06-09 12:55:31.956 W/SocketClient( 198): write error (Broken pipe) 16:24:37 06-09 16:17:43.528 W/GeckoConsole( 1285): [JavaScript Error: "NS_ERROR_NOT_INITIALIZED: Component returned failure code: 0xc1f30001 (NS_ERROR_NOT_INITIALIZED) [nsIMessageSender.sendAsyncMessage]" {file: "chrome://specialpowers/content/SpecialPowersObserver.js" line: 103}] Expected result: the test kept going Actual result: the task and test never goes on.
Blocks: MTBF-B2G
Summary: [MTBF] → [MTBF] W/SocketClient( 198): write error (Broken pipe)
tracking-b2g: --- → +
Walter, could you help to update more information?
Flags: needinfo?(wachen)
the request should go to Paul now.
Flags: needinfo?(wachen) → needinfo?(pyang)
havent seen this error for long time. close as wfm.
Status: NEW → RESOLVED
Closed: 10 years ago
Flags: needinfo?(pyang)
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.