SamantazFox has quit [Read error: Connection reset by peer]
SamantazFox has joined #openscad
guso51 has quit [Quit: Client closed]
misterfish has quit [Ping timeout: 250 seconds]
teepee_ has joined #openscad
_whitelogger has joined #openscad
gwillen has joined #openscad
aiyion has joined #openscad
misterfish has joined #openscad
qeed_ has joined #openscad
qeed has quit [Ping timeout: 245 seconds]
mmu_man has joined #openscad
ToAruShiroiNeko has quit [Ping timeout: 246 seconds]
To_Aru_Shiroi_Ne has joined #openscad
To_Aru_Shiroi_Ne is now known as ToAruShiroiNeko
L29Ah has left #openscad [#openscad]
L29Ah has joined #openscad
snaked has quit [Quit: Leaving]
gwillen has quit [Ping timeout: 246 seconds]
gwillen has joined #openscad
rvt has quit [Ping timeout: 258 seconds]
rvt has joined #openscad
LordOfBikes has joined #openscad
arogora has joined #openscad
killjoy has quit [Ping timeout: 264 seconds]
arogora is now known as killjoy
killjoy has joined #openscad
killjoy has quit [Changing host]
J23k56 has quit [Ping timeout: 246 seconds]
mmu_man has quit [Ping timeout: 250 seconds]
kintel has joined #openscad
<kintel>
Does anyone have experience with OpenSCAD's code coverage? Looking briefly at the setup, it looks like parallel test runs are not really managed, so I expect `ctest -j20` to yield partial results
marco[m] has joined #openscad
<kintel>
I also noticed this interesting line of code: tar -C tests/.gcov -c -f - . | tar -x -f -
kintel has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
mmu_man has joined #openscad
kintel has joined #openscad
J23k56 has joined #openscad
Guest41 has quit [Ping timeout: 246 seconds]
misterfish has quit [Ping timeout: 250 seconds]
<InPhase>
kintel: That would be peeps[zen] who worked with that infrastructure.
kintel has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
mmu_man has quit [Ping timeout: 245 seconds]
mmu_man has joined #openscad
<peeps[zen]>
InPhase, kintel: i don't think I did much with code coverage. i've looked at the reports a couple times but I thought teepee mostly set them up
<peeps[zen]>
maybe youre' thinking of my somewhat recent mucking about with clang-tidy, but that's linter not coverage
<teepee>
peeps[zen]: helped fixing it sometime later as for some reason the collection of results and uploading as artifacts tends to break every now and then
kintel has joined #openscad
<teepee>
I have not looked at it for a while, so it's possible that it broke again
<InPhase>
peeps[zen]: Actually I think I was thinking of your profiling work. (That's bundled into one feature family in the config, which is how my mind went there.)
<kintel>
It seems to still work, but I don't think it gives correct results for parallel test executions
kintel has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
<peeps[zen]>
regarding the "interesting line" though, it looks like its essentially copying a subdirectory. is that any different from doing something like "cp -R tests/.gcov ./"
<peeps[zen]>
or maybe i'm reading it wrong
kintel has joined #openscad
<kintel>
yeah, looks like it's just copying files. I was just confused as there is both a build/.gcov and a build/tests/.gcov