Line length is restricted in latest Gitlab Runner of Gitlab.com

I have a few jobs in gitlab.com that suddenly failed since last Thu (I think). After some debugging, I found that if in job log, anything output a line longer than 2k (I guess), the job is stopped before the line appears in log.

Is this change on purpose? I know output a very long line is stupid, but sometimes it is a tool I cannot control.

Hi @shida2
if your Job output exceeds the limit, no more output is shown, but the status of the job is properly discovered. You should also get a warning in the Job output about this Job's log exceeded limit xxx bytes. Do you get this message?

No. And in my case, it is not the whole log exceeds some limitation, but just one line. The line was a compact json with some base64 text. The job (using docker in docker service) returns 137 before the line was shown in log. If I hid the output of the line, the job succeeded.

PS: in succeeded job, there are quite lot of text output after “the line”, so I do not think it triggered the “whole log limitation”.

Error 137 is usually returned by Docker in case of “Out of Memory” errors.
Are you using the Shared Runners or do you have your own?

I am using Shared. And I am using DinD, 137 was returned by docker run, which makes it also possible for container was stopped.

Another case I got today, in a different organization. A very long line output causing the job log shown in webpage being trunked to only last few lines. Raw log is alright.

Is this configurable?Another case I got today, in a different organization. A very long line output causing the job log shown in webpage being trunked to only last few lines. Raw log is alright.

Is this configurable?