Closed
Bug 1168045
Opened 10 years ago
Closed 8 years ago
[MTBF][Marionette] Python Marionette network having issues after continuous browser tests
Categories
(Remote Protocol :: Marionette, defect)
Tracking
(Not tracked)
RESOLVED
INCOMPLETE
People
(Reporter: wachen, Unassigned)
References
Details
Attachments
(1 file)
37.64 KB,
image/png
|
Details |
STR:
1. using MTBF operation to start a MTBF run, please set the json file to be flame_browser.json.
2. After few test cases, it started to not able to connect to the local server Marionette set up.
Please see the attachment pictures.
Reporter | ||
Updated•10 years ago
|
Component: MTBF → Marionette
Product: Firefox OS → Testing
Updated•9 years ago
|
Comment 1•9 years ago
|
||
What makes you think this is marionette that is failing and not the something inside B2G? Marionette will just be telling gecko to load up the network resource so it would be great if we could clarify
Flags: needinfo?(wachen)
Reporter | ||
Comment 2•9 years ago
|
||
I think that we encountered this kind of issues a lot after running MTBF. (turning on and off wifi frequently) Also, there are logs in logcat indicating network interface is having some issues at that time.
Flags: needinfo?(wachen) → needinfo?(pyang)
Comment 3•9 years ago
|
||
Can we move this over to Necko then maybe?
Comment 4•9 years ago
|
||
(In reply to David Burns :automatedtester from comment #3)
> Can we move this over to Necko then maybe?
Not go very far for the module but look possible.
do we have plan to integrate or wrap it for test harness?
Flags: needinfo?(pyang)
Comment 5•8 years ago
|
||
B2G related so closing
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → INCOMPLETE
Updated•2 years ago
|
Product: Testing → Remote Protocol
You need to log in
before you can comment on or make changes to this bug.
Description
•