[Nautilus-LTE] Cellular AutoConnect test fails to setProperties and error's out with Error.CannotChangeSharedConfig |
||||||
Issue description
Chrome Version: R68-10718.88.0
OS: Chrome OS
What steps will reproduce the problem?
(1) Run cellular_ChromeEndToEnd.autoconnectCellular test.
(2) Test fails.
(3)
What is the expected result?
Test should pass
What happens instead?
08/23 12:55:57.963 DEBUG|network_ChromeCell:0134| Cellular service: {u'Priority': 0, u'Connectable': True, u'ConnectionState': u'Connected', u'Source': u'Device', u'Cellular': {u'ActivationState': u'Activated', u'Scanning': False, u'RoamingState': u'Home', u'NetworkTechnology': u'LTE', u'SignalStrength': 25}, u'GUID': u'07ecac05-5335-4e67-8f1f-6ce4d4b15030', u'Type': u'Cellular', u'Name': u'Verizon Wireless'}
08/23 12:55:57.963 DEBUG|network_ChromeCell:0057| _set_autoconnect
08/23 12:55:57.970 DEBUG|inspector_websocke:0103| sent [{
"id": 18,
"method": "Runtime.evaluate",
"params": {
"expression": "chromeTesting.networking.setProperties(\"07ecac05-5335-4e67-8f1f-6ce4d4b15030\", {\"Cellular\": {\"AutoConnect\": true}});; 0;",
"returnByValue": true
}
}]
08/23 12:55:57.973 DEBUG|inspector_websocke:0170| got [{
"id": 18,
"result": {
"result": {
"description": "0",
"type": "number",
"value": 0
}
}
}]
08/23 12:55:57.980 DEBUG|inspector_websocke:0103| sent [{
"id": 19,
"method": "Runtime.evaluate",
"params": {
"expression": "chromeTesting.networking.callStatus.setProperties",
"returnByValue": true
}
}]
08/23 12:55:57.981 DEBUG|inspector_websocke:0170| got [{
"id": 19,
"result": {
"result": {
"type": "object",
"value": {
"error": "Error.CannotChangeSharedConfig",
"result": null,
"status": "chrome-test-call-status-failure"
}
}
}
}]
08/23 12:55:57.983 DEBUG|inspector_websocke:0103| sent [{
"id": 20,
"method": "Runtime.evaluate",
"params": {
"expression": "chromeTesting.networking.callStatus.setProperties",
"returnByValue": true
}
}]
08/23 12:55:57.984 DEBUG|inspector_websocke:0170| got [{
"id": 20,
"result": {
"result": {
"type": "object",
"value": {
"error": "Error.CannotChangeSharedConfig",
"result": null,
"status": "chrome-test-call-status-failure"
}
}
}
}]
08/23 12:55:57.985 INFO |chrome_networking_:0115| ChromeNetworkingTestContext: teardown
08/23 12:55:57.986 DEBUG| global_hooks:0056| ['sh', '-c', '/bin/ps --no-headers -A -o pid,ppid,args:4096,state']
,
Sep 12
,
Sep 12
We only allow the networkingPrivate API to change unshared (i.e. user) network configurations, except in WebUI (i.e. Settings). Since the Cellular service is effectively always shared, we may need to add an exception for the autotest extension.
,
Sep 12
Logs can be found @ https://stainless.corp.google.com/browse/chromeos-autotest-results/231599073-chromeos-test/
,
Oct 31
Hi Steven, Test still fails with this exception. Can you please take a look into this fix?
,
Nov 1
I don't know anything about this test, where it lives, or who owns it, but I would expect this to be owned by the Shill team? benchan@, thoughts? My personal preference would be to have someone working on Shill to re-write these tests for Tast, but that would be a pretty significant effort.
,
Nov 1
I wrote the cellular_ChromeEndToEnd test and we didn't use to get this error. >>>>Since the Cellular service is effectively always shared, we may need to add an exception for the autotest extension. Will this fix the error? Where exactly do we add this exception for autotest? In regards to Tast, we currently don't have plans/bandwidth to convert existing tests over. Maybe in the future.
,
Nov 1
Maybe? I'm really not super familiar with autotest. I don't know why it started failing, I was just speculating. If it started failing recently, I would expect something else to be the cause.
,
Nov 16
|
||||||
►
Sign in to add a comment |
||||||
Comment 1 by harpreet@chromium.org
, Aug 23Summary: Cellular AutoConnect test fails to setProperties and error's out with Error.CannotChangeSharedConfig (was: Cellular AutoConnect test is failing with reason ""setProperties" did not return with status SUCCESS:")