АА
и запустите его с такими же аргументами как в доках...
Size: a a a
2020 July 02
В
Большое спасибо!
2020 July 03
k
всем привет, можно тут задать вопрос по использованию ggr?
MT
всем привет, можно тут задать вопрос по использованию ggr?
Думаю что да
k
Ок , вопрос такой, я подключил к ggr 6 машин, на каждой limit сессий ограничен по числу ядер от 4 до 6, при этом в квота файле count для балансировки прописал такой же как limit. При запуске тестов в 20 потоков периодически вижу вот такое в логах
k
2020/07/03 09:25:31 [1] [0.00s] [SESSION_ATTEMPTED] [test] [ip] [firefox-76.0] [host3] [-] [1] [-]
2020/07/03 09:25:31 [3] [0.00s] [SESSION_ATTEMPTED] [test] [ip] [firefox-76.0] [host6] [-] [1] [-]
2020/07/03 09:25:31 [4] [0.00s] [SESSION_ATTEMPTED] [test] [ip] [firefox-76.0] [host4] [-] [1] [-]
2020/07/03 09:25:31 [2] [0.00s] [SESSION_ATTEMPTED] [test] [ip] [firefox-76.0] [host2] [-] [1] [-]
2020/07/03 09:25:31 [0] [0.01s] [SESSION_ATTEMPTED] [test] [ip] [firefox-76.0] [host3] [-] [1] [-]
2020/07/03 09:25:31 [6] [0.00s] [SESSION_ATTEMPTED] [test] [ip] [firefox-76.0] [host4] [-] [1] [-]
2020/07/03 09:25:31 [7] [0.00s] [SESSION_ATTEMPTED] [test] [ip] [firefox-76.0] [host4] [-] [1] [-]
2020/07/03 09:25:31 [5] [0.00s] [SESSION_ATTEMPTED] [test] [ip] [firefox-76.0] [host3] [-] [1] [-]
2020/07/03 09:25:31 [8] [0.00s] [SESSION_ATTEMPTED] [test] [ip] [firefox-76.0] [host2] [-] [1] [-]
2020/07/03 09:25:31 [9] [0.00s] [SESSION_ATTEMPTED] [test] [ip] [firefox-76.0] [host3] [-] [1] [-]
2020/07/03 09:25:31 [10] [0.00s] [SESSION_ATTEMPTED] [test] [ip] [firefox-76.0] [host4] [-] [1] [-]
2020/07/03 09:25:31 [11] [0.00s] [SESSION_ATTEMPTED] [test] [ip] [firefox-76.0] [host5] [-] [1] [-]
2020/07/03 09:25:31 [12] [0.00s] [SESSION_ATTEMPTED] [test] [ip] [firefox-76.0] [host4] [-] [1] [-]
2020/07/03 09:25:31 [13] [0.01s] [SESSION_ATTEMPTED] [test] [ip] [firefox-76.0] [host4] [-] [1] [-]
2020/07/03 09:25:31 [14] [0.01s] [SESSION_ATTEMPTED] [test] [ip] [firefox-76.0] [host3] [-] [1] [-]
2020/07/03 09:25:31 [15] [0.00s] [SESSION_ATTEMPTED] [test] [ip] [firefox-76.0] [host4] [-] [1] [-]
2020/07/03 09:25:31 [15] [0.00s] [SESSION_FAILED] [test] [ip] [firefox-76.0] [host6] [-] [1] [Too Many Requests]
2020/07/03 09:25:31 [15] [0.00s] [SESSION_ATTEMPTED] [test] [ip] [firefox-76.0] [host2] [-] [2] [-]
2020/07/03 09:25:31 [16] [0.00s] [SESSION_ATTEMPTED] [test] [ip] [firefox-76.0] [host3] [-] [1] [-]
2020/07/03 09:25:31 [17] [0.00s] [SESSION_ATTEMPTED] [test] [ip] [firefox-76.0] [host6] [-] [1] [-]
2020/07/03 09:25:31 [18] [0.00s] [SESSION_ATTEMPTED] [test] [ip] [firefox-76.0] [host5] [-] [1] [-]
2020/07/03 09:25:31 [19] [0.00s] [SESSION_ATTEMPTED] [test] [ip] [firefox-76.0] [host1] [-] [1] [-]
k
нормально ли что я вижу SESSION_FAILED на некоторых хостах?
k
и как понять ошибку Too Many Requests, что имеется в виду?
DZ
а гуглплей сервисы были включены?
При билде имеджа скриптом выбирал image type = google_apis_playstore. С ним нужны какие-то дополнительные танцы?
MF
оно просто не работает)
BP
Hey 🙂
BP
I'm trying to deploy moon on EKS
I've completed the depyloyment, and this is my
I've completed the depyloyment, and this is my
kubectl get svc -n moon output:BP
NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE
browsers ClusterIP None <none> <none> 46m
moon LoadBalancer 10.100.118.252 a597ce25ea4bc4fc1bfc5fd36562b450-364482419.eu-central-1.elb.amazonaws.com 4444:31721/TCP,8080:30826/TCP 46m
BP
But when accessing
http://10.100.118.252:4444/wd/hub or using the domain, nothing loads there's a connection timeoutBP
Ok, i think i had to little hardware on my cluster,
now it's working
now it's working
IK
Ok, i think i had to little hardware on my cluster,
now it's working
now it's working
that's great. sometimes this could be because of firewall issues, when port is 4444 is closed in security group settings
DZ
оно просто не работает)
аа, спасибо. Попробую другой type
BP
Another issue after deployment
The moon deployment is up and running at http://a597ce25ea4bc4fc1bfc5fd36562b450-364482419.eu-central-1.elb.amazonaws.com:8080/#/
I'm trying to create playwright session and getting timeout
The moon deployment is up and running at http://a597ce25ea4bc4fc1bfc5fd36562b450-364482419.eu-central-1.elb.amazonaws.com:8080/#/
I'm trying to create playwright session and getting timeout
BP
/* eslint-disable */
const playwright = require('playwright');
async function start() {
const browser = await playwright.chromium.connect({
wsEndpoint: 'ws://a597ce25ea4bc4fc1bfc5fd36562b450-364482419.eu-central-1.elb.amazonaws.com:4444/playwright/chromium',
timeout: 120 * 1000
});
try {
const context = await browser.newContext();
const page = await context.newPage();
await page.goto('https://wikipedia.com');
console.log(await page.title());
} finally {
await browser.close();
}
}
start();
that's my code
BP
(node:54051) UnhandledPromiseRejectionWarning: Error: WebSocket error: socket hang up
================== chromium.connect logs ==================
<ws connecting> ws://a597ce25ea4bc4fc1bfc5fd36562b450-364482419.eu-central-1.elb.amazonaws.com:4444/playwright/chromium
<ws connect error> ws://a597ce25ea4bc4fc1bfc5fd36562b450-364482419.eu-central-1.elb.amazonaws.com:4444/playwright/chromium socket hang up
<ws disconnected> ws://a597ce25ea4bc4fc1bfc5fd36562b450-364482419.eu-central-1.elb.amazonaws.com:4444/playwright/chromium
that's the error (looks like it's the timeout)