Closed Bug 1168045 Opened 9 years ago Closed 7 years ago

[MTBF][Marionette] Python Marionette network having issues after continuous browser tests

Categories

(Remote Protocol :: Marionette, defect)

ARM
Gonk (Firefox OS)
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED INCOMPLETE

People

(Reporter: wachen, Unassigned)

References

Details

Attachments

(1 file)

Attached image 2015-05-25-15-55-36.png
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.
Blocks: MTBF-meta
Component: MTBF → Marionette
Product: Firefox OS → Testing
Blocks: MTBF-Marionette
No longer blocks: MTBF-meta
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)
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)
Can we move this over to Necko then maybe?
(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)
B2G related so closing
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → INCOMPLETE
Product: Testing → Remote Protocol
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: