firmware_ConsecutiveBoot test

59 views
Skip to first unread message

T.H. Lin

unread,
Aug 26, 2014, 3:44:19 AM8/26/14
to faft-...@chromium.org

Dear FAFT-Group,

 I do firmware_ConsecutiveBoot test, and I met a un-known issue….

 Why testing show class ‘socket.error’ after Retryng…..? It did not happen on my previous packages/test! Network issue? Or,??

Please help to give some info to let me change FAFT/autotest package…

 

B.R.

T.H.

 

08/25 04:49:20.609 INFO | test_that:0144| autoserv| <class 'socket.error'>([Errno 111] Connection refused)

08/25 04:49:20.609 INFO | test_that:0144| autoserv| Retrying in 0.653930 seconds...

08/25 04:49:21.271 INFO | test_that:0144| autoserv| <class 'httplib.BadStatusLine'>('')

08/25 04:49:21.272 INFO | test_that:0144| autoserv| Retrying in 1.454285 seconds...

08/25 04:49:22.732 INFO | test_that:0144| autoserv| <class 'httplib.BadStatusLine'>('')

08/25 04:49:22.733 INFO | test_that:0144| autoserv| Retrying in 0.745755 seconds...

test_that.DEBUG
Reply all
Reply to author
Forward
0 new messages