<areinking>
Does anyone know off-hand if simple HTML formatting (e.g. bold, fixed-width) is allowed in build step names?
kveremitz has joined #buildbot
kveremitz has quit [Read error: Connection reset by peer]
kveremitz has joined #buildbot
areinking has quit [Quit: Connection closed]
tflink has quit [Ping timeout: 256 seconds]
tflink_ has joined #buildbot
koobs has quit [Ping timeout: 260 seconds]
kraiskil has joined #buildbot
de-vri-es has quit [Ping timeout: 240 seconds]
de-vri-es has joined #buildbot
kraiskil has quit [Ping timeout: 256 seconds]
kkleine has joined #buildbot
kkleine has quit [Remote host closed the connection]
kkleine has joined #buildbot
de-vri-es has quit [Ping timeout: 272 seconds]
de-vri-es has joined #buildbot
thm has joined #buildbot
<thm>
I see a good amount of tmp_pack_XXXXXX files in gitpoller-work/objects/pack, eating up my disk space. any idea what causes this and how to avoid/fix?
<thm>
the master is 2.10.0 with python 3.6.8 on centos7, git 1.8.3.1
kkleine has quit [Remote host closed the connection]
alicef_ has quit [Quit: Bridge terminating on SIGTERM]
alicef_ has joined #buildbot
kkleine has joined #buildbot
jcarl43 has joined #buildbot
kkleine has quit [Ping timeout: 244 seconds]
kraiskil has joined #buildbot
kraiskil has quit [Ping timeout: 256 seconds]
<thm>
is it safe to run 'git gc' in the gitpoller-work directory?
kraiskil has joined #buildbot
nand0p has quit [*.net *.split]
nand0p has joined #buildbot
<thm>
nvm, found the issue
<felixfontein>
out of curiosity: what was the issue?
<felixfontein>
(I checked in our instance, it does not have these tmp files)
<thm>
I had an object file with wrong contents (this frightens me a little bit, but anyway...), and git gc actually refused to work
<thm>
I renamed that file, fetched it contents from a checkout elsewhere and re-inserted it using git hash-object -w
<thm>
and voila, git gc is happy again, and no additional tmp files
<thm>
(took a while to figure it all out, though)
<felixfontein>
hmm, that's indeed scary :)
<felixfontein>
maybe just removing the directory and restarting buildbot would have also solved it
<thm>
yes, but now I learned something
<thm>
:D
<felixfontein>
:)
<thm>
actually, I only noticed because another container in that docker instance started to malfunction because of the disk full situation
<thm>
maybe I need to learn how to quota docker volumes
kraiskil has quit [Ping timeout: 256 seconds]
kraiskil has joined #buildbot
kraiskil has quit [Ping timeout: 240 seconds]
dol-sen has quit [Remote host closed the connection]