Hi, I have a test run that needs to log failed result on terminal screen in Gitlab Runner.
Everything was fine until runner suddenly marked the test run as failed, checking a little bit, I took a wild guess that Gatling may reach the maximum log size on terminal. Is there a way that I could increase the terminal log limit in Gatling?
.
Although I may be mistaken, I remembered that if Gatling reaches log size, it will simply continue to run without any terminal output. Can I get confirm on this too ?
.
Thanks for helping me
Hi Samir,
Sadly, Runner terminated itself while Gatling log was still on-screen. But you can try with some test that returns lots of data to quickly fill up.
But yes I don’t heavily doubt Gatling on this, but if it were Runner side, it may show something as
“Job log has been exceeded x size”
Hi @Samir
I’ve encountered this issue again, but I connected directly to Runner and saw that Gatling is still running, only Runner’s side got problem.
So to avoid this, I have increased writeInterval period from 5s to 60s, now everything is okay.
Thanks for your kind help.