Hi Pavel,

On 24/11/2020 18:44, Pavel Machek wrote:
> Hi!
> 
>> This is going on for a few days now, but today it seems worse than
>> usual:
>>
>> https://gitlab.com/cip-project/cip-kernel/linux-cip/-/pipelines/220169843
>>
>> builds are failing, 'HTTP 500 curl 22' error, so not a real build
>> problem. I can probably just click restart... 6 times. But something
>> is not there, and it is getting worse.
> 
> Today I got new one....
> 
> Waiting for pod gitlab/runner-bcrayztp-project-2678032-concurrent-392fb6 to be running, status is Pending
> 217Running on runner-bcrayztp-project-2678032-concurrent-392fb6 via cip-project-v3-gitlab-runner-6dbd79945f-wdqqw...
> 219
> Fetching changes with git depth set to 10...
> 00:35
> 220Initialized empty Git repository in /builds/cip-project/cip-kernel/linux-cip/.git/
> 221Created fresh repository.
> 222error: RPC failed; curl 92 HTTP/2 stream 0 was not closed cleanly: INTERNAL_ERROR (err 2)
> 223fatal: the remote end hung up unexpectedly
> 224fatal: early EOF
> 225fatal: index-pack failed
> 227
> Uploading artifacts.
> 
> I wonder... Is each of our workers pulling full copy of kernel from
> gitlab?
> 
> If so, I understand that gitlab might be a bit unhappy. We probably
> should populate the initial version from our servers (or from
> kernel.org), or maybe include copy of recent linux directly into
> machine images... to reduce load on gitlab.

Maybe you can consider using git depth of 1.


-- 
Regards
Sudip