We used to run tests in single job (tests were running in parallel) and everything was fine.
Recently we divided the tests into multiple jobs but when we run the jobs (which run the tests in sequence) some tests fail with this message:
Could not start a new session. New session request timed out
There are 10 jobs each by average contain 8 tests that are running against a remoter agent in GCP(google cloud platform) Linux/Docker in headless mode with 6 workers:
8vCpu, 12GB Ram, SSD storage
If I just run 1 job that had failed tests, it would pass (no session timeout)!
I reduced the worker count to 4 but still same issue.
Hi @reza ,
First of all, welcome to our community .
Please do the following to help us identify the issue:
- Restart your Agent
- Reproduce the issue you encountered
- Send us the agent logs of today for analysis.
You can download the logs as shown below:
And please send the logs to our: email@example.com
Thanks for your reply.
I can’t see “Download logs” option when opening the menu.
(available options are: Copy ID - Edit Tags - Delete agent)
Is there anything I’m missing? (maybe enabling a flag when running with docker?)
This is my docker-compose.yml:
TP_AGENT_ALIAS: "e2-highcpu-8 testproject-5"
I have the same issue. I don’t see any “Download logs” option for my TestProject agent set up via Docker. Does anyone know how to get the logs / why they’re not present?
Hi @apoorv @reza ,
The correct way to find the docker logs is to check the folder in the path you put in the volumes:
Let me know if you managed.