Device Farm test setup fails due to 'ascii' codec can't decode byte

0

I am trying to run Appium Python tests for Android devices. However, my test setup fails with the following error: 'ascii' codec can't decode byte 0xcc in position 58: ordinal not in range(128). My tests run locally just fine, and from the limited information in the logs here I'm unable to decipher where the problem lies. What steps can I take to troubleshoot this issue?

Entirety of test setup log is below:

[{"attachment_id": null, "parent_id": null, "timestamp": "2022-04-12T23:02:46.018578Z", "level": "Info", "pid": 3106, "data": "Starting Setup Suite", "source": "Harness", "tag": null, "subtype": "Text", "tid": 3111, "type": "Message", "id": 13},
{"attachment_id": null, "parent_id": null, "timestamp": "2022-04-12T23:02:46.019150Z", "level": "Info", "pid": 3106, "data": "Starting Setup Test", "source": "Harness", "tag": null, "subtype": "Text", "tid": 3111, "type": "Message", "id": 15}, 
{"attachment_id": null, "parent_id": null, "timestamp": "2022-04-12T23:02:48.555726Z", "level": "Debug", "pid": 31496, "data": "Binder ioctl to enable oneway spam detection failed: Invalid argument", "source": "Device", "tag": "ProcessState", "subtype": "Text", "tid": 31496, "type": "Message", "id": 16}, 
{"attachment_id": null, "parent_id": null, "timestamp": "2022-04-12T23:02:52.875809Z", "level": "Errored", "pid": 3106, "data": "'ascii' codec can't decode byte 0xcc in position 58: ordinal not in range(128)", "source": "Harness", "tag": null, "subtype": "Text", "tid": 3127, "type": "Message", "id": 17}, 
{"attachment_id": null, "parent_id": null, "timestamp": "2022-04-12T23:02:53.334113Z", "level": "Errored", "pid": 3106, "data": "'ascii' codec can't decode byte 0xcc in position 58: ordinal not in range(128)", "source": "Harness", "tag": null, "subtype": "Text", "tid": 3111, "type": "Message", "id": 22}, 
{"attachment_id": null, "parent_id": null, "timestamp": "2022-04-12T23:02:53.334757Z", "level": "Info", "pid": 3106, "data": "Finished Setup Test", "source": "Harness", "tag": null, "subtype": "Text", "tid": 3111, "type": "Message", "id": 24}, 
{"attachment_id": null, "parent_id": null, "timestamp": "2022-04-12T23:02:53.336363Z", "level": "Info", "pid": 3106, "data": "Finished Setup Suite", "source": "Harness", "tag": null, "subtype": "Text", "tid": 3111, "type": "Message", "id": 27}]
  • Hi. Can you share the test code that causes the problem?

posta 2 anni fa265 visualizzazioni
2 Risposte
0
Risposta accettata

The problem was some unused files that someone had snuck into the repo (specifically a .xlsx file). Removing those files from the test bundle solved the issue.

con risposta 2 anni fa
0

Hello ,

Thank you for reaching out to us.

From the above correspondence, I see that issue already got resolved. Please let us know if you are still facing the issue ?

AWS
TECNICO DI SUPPORTO
con risposta 2 anni fa

Accesso non effettuato. Accedi per postare una risposta.

Una buona risposta soddisfa chiaramente la domanda, fornisce un feedback costruttivo e incoraggia la crescita professionale del richiedente.

Linee guida per rispondere alle domande