FoxComm / highlander

Because there can only be one
MIT License
9 stars 3 forks source link

[Phoenix] API call fail with timeout. #1893

Open alexanderfc opened 7 years ago

alexanderfc commented 7 years ago

Here's what failed due to SocketTimeoutException during one of ui-automation test runs (brackets hold the number of failures of that call across multiple different tests):

I've checked reports of ui-automation scheduled night builds since 17th of May, and only test run from 19th of May had nearly this amount of timeouts (11 to be precise). All the rest had 1-2 failures due to timeouts. In addition to what's listed above, there were failures in calls to /v1/inventory/summary/{skuCode} and admin auth /v1/public/login both of which happened only once.

So mostly it's a cart. Also, some tests failing because /admin/carts/{refNum} page loading hangs when accessing it by direct url.

alexanderfc commented 7 years ago

UPD: a couple of days in a row none of routes listed in the description have failed with timeout. But, today I've run selenium tests locally against test env, and one test has failed with timeout hitting /v1/customers/{customerId}/payment-methods/credit-cards rout (create credit card as an admin via direct API call). Also, during the same period, all cart tests were passing and haven't even been retried.

annappropriate commented 7 years ago

Related: https://github.com/FoxComm/highlander/issues/1612 https://github.com/FoxComm/highlander/issues/1808