[08:06:49] <gehel>	 dcausse, zpapierski: around? Time for a quick chat about hiring and technical tasks?
[08:07:01] <dcausse>	 sure
[08:07:05] <zpapierski>	 one sec, having a call
[08:07:44] <gehel>	 meet.google.com/fng-bscg-dsh
[08:07:50] <gehel>	 zpapierski: ping us when you're free
[08:09:03] <zpapierski>	 like a phone call, I'm free now :)
[09:37:48] <gehel>	 lunch + errand
[09:49:00] <dcausse>	 errand+lunch
[10:05:06] <zpapierski>	 lunch, no errands, but relocated required
[13:12:35] <zpapierski>	 gehel: https://gerrit.wikimedia.org/r/c/wikimedia-event-utilities/+/699948 - don't we want to fail the build for decreased mutation coverage?
[13:13:05] <zpapierski>	 apart from that, two thumbs up for pitest, 30 seconds is a worthy sacrifice (Iremember this being much more substantial)
[13:13:18] <gehel>	 that's something we should do with Sonar.
[13:13:51] <zpapierski>	 true, we don't fail for decreased coverage either
[13:14:02] <gehel>	 I don't think pitest has a good way to do differential analysis, except whatever isn't committed in SCM
[13:14:18] <gehel>	 I'm also not sure that mutation coverage is a great metric
[13:14:38] <gehel>	 I think that mutation testing is more interesting as a tool to look at when you code
[13:14:55] <gehel>	 but it requires more thinking than just applying a metric
[13:15:27] <zpapierski>	 I think it's a better metric than code coverage (which, admittedly, is a low bar), but I see your point 
[13:18:29] <gehel>	 looks like there is some support for git, but commercial only (with free licence for opensource projects): https://blog.pitest.org/pitest-pr-setup/
[13:23:39] <gehel>	 I saw an article from Henry Coles about his workflow with PIT.
[13:23:43] * gehel needs to find it back
[13:30:35] <gehel>	 there are plugins to integrate PIT into Sonar, but we can't deploy plugins to sonarcloud
[13:31:01] <gehel>	 Might be worth asking SonarSource if they could add PIT support to SonarCloud?
[13:32:29] <gehel>	 what we should really have is a mix of PIT and Infinitest, well integrated into our IDEs
[13:34:28] <gehel>	 http://blog.pitest.org/dont-let-your-code-dry/
[13:34:53] <zpapierski>	 infinitest, that's the name I haven't heard in a long while
[13:35:16] <zpapierski>	 I wasn't even aware it works now correctly with IntelliJ, when I switched from Eclipse, it didn't
[13:35:24] <zpapierski>	 (auto saving was messing with the formula)
[13:43:43] <zpapierski>	 this article made me think if maybe it makes sense at all to add mutation tests to CI
[13:44:02] <zpapierski>	 I'd love to try out pitest with Infinitest 
[13:50:07] <dcausse>	 errand
[13:57:50] <zpapierski>	  I still can't access cindy host :(
[14:00:57] <zpapierski>	 gehel: by any chance your magic linux skill include knowledge what this could mean?
[14:01:03] <zpapierski>	 https://www.irccloud.com/pastebin/7mGKJfC2/
[14:01:27] <zpapierski>	 it's right after server accepted my rsa key
[14:04:03] <gehel>	 that's not the full log?
[14:04:25] <gehel>	 which bastion?
[14:05:52] <zpapierski>	 lemme check ( I always forget)
[14:18:09] <zpapierski>	 I wasn't a member of a project - all good now, thanks to gehel :)
[14:19:23] <gehel>	 zpapierski (and maybe dcausse?): want to chat a bit about PIT and what we should or should not do around it?
[14:19:39] <zpapierski>	 sure
[14:19:46] <dcausse>	 sure
[14:19:53] <gehel>	 meet.google.com/bzc-utdt-tjk
[15:19:39] <zpapierski>	 dcausse: where can I find logs from cindy run? they scroll by a bit too fast :)
[15:28:11] <dcausse>	 zpapierski: on the host the output is saved in /tmp/cindy.log or per build on the vagrant container (cd /srv/mediawiki-vagrant && vagrant ssh) in /tmp/cindy_run.XXXX.log where XXXX is the gerrit patch ID 
[15:28:25] <zpapierski>	 awesome, thx!