Closed
Bug 1003043
Opened 10 years ago
Closed 9 years ago
[MTBF][Marionette] Some exception caught during test running
Categories
(Remote Protocol :: Marionette, defect, P3)
Tracking
(Not tracked)
RESOLVED
INCOMPLETE
People
(Reporter: wachen, Unassigned)
References
Details
(Keywords: pi-marionette-client, Whiteboard: [affects=mtbf][affects=b2gdevice])
Attachments
(2 files)
http://mtbf-1.corp.tpe1.mozilla.com:8080/job/hamachi.v140.mtbf/label=master/18/console 03:41:23 raise IOError("%s: Connection to Marionette server is lost. Check gecko.log (desktop firefox) or logcat (b2g) for errors." % str(e)) 03:41:23 IOError: [Errno 32] Broken pipe: Connection to Marionette server is lost. Check gecko.log (desktop firefox) or logcat (b2g) for errors.
Reporter | ||
Comment 1•10 years ago
|
||
Memory Report: http://mtbf-1.corp.tpe1.mozilla.com:8080/job/hamachi.v140.mtbf/label=master/lastSuccessfulBuild/artifact/tests/python/gaia-ui-tests/gaiatest/about-memory.zip
Reporter | ||
Comment 2•10 years ago
|
||
Comment 3•10 years ago
|
||
This one is weird. After 10 hours running, marionette server suddenly disconnected and client raised a IOError: Broken pipe. When I tried to start a session, it worked like nothing happened. From marionette_test.py, we catch IOError but only socket.error, if this sort of behavior is expected, do we need to catch this exception as well?
Comment 4•10 years ago
|
||
Yes, we should catch both socket.error and IOError. Do you mean here: https://mxr.mozilla.org/mozilla-central/source/testing/marionette/client/marionette/marionette_test.py#297 or is there another place we're missing this exception? I noticed that the logcat that's attached doesn't have any Marionette output. Is this because the logcat was generated long after the test was over, or is there just no output from marionette? If it is the latter, do you see any output if you have a session and using marionette actively?
Comment 5•10 years ago
|
||
Yes, #297 should be the right place. We didn't attach logcat during whole test run. Will try to add and run again, see if we can gather more information.
Updated•10 years ago
|
Keywords: ateam-marionette-client
Whiteboard: [affects=mtbf]
Reporter | ||
Updated•10 years ago
|
Reporter | ||
Updated•10 years ago
|
Reporter | ||
Updated•10 years ago
|
Updated•10 years ago
|
Whiteboard: [affects=mtbf] → [affects=mtbf][affects=b2gdevice]
Comment 6•9 years ago
|
||
Paul, exceptions are still exist? If not, could we close bug?
Flags: needinfo?(pyang)
OS: Linux → Gonk (Firefox OS)
Hardware: x86_64 → ARM
Updated•9 years ago
|
Priority: -- → P3
Comment 7•9 years ago
|
||
Not seeing similar ones. If we consider latest marionette server lost, I guess this bug can be dupped.
Flags: needinfo?(pyang)
Comment 8•9 years ago
|
||
We have a new bug to track for all relative issues.
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → INCOMPLETE
Updated•1 year ago
|
Product: Testing → Remote Protocol
You need to log in
before you can comment on or make changes to this bug.
Description
•