[12:51:48] Is there a way to run all the deploy-charts tests locally? I have a fairly extensive networkpolicy change (https://gerrit.wikimedia.org/r/c/operations/deployment-charts/+/1054280?tab=checks) and the CI tests keep timing out after 30m [12:52:30] klausman: so there's a Rakefile action but I don't have ruby/rake installed so that never works for me [12:52:32] instead I do: [12:52:37] sudo docker run --pull always --user 1000 --rm -v `pwd`:/src:rw -v /etc/passwd:/etc/passwd:ro -v /etc/group:/etc/group:ro docker-registry.wikimedia.org/releng/helm-linter:latest [12:53:08] ty, will give that a go [13:00:11] klausman: rake run_locally [13:00:24] I will give that a go as well [13:00:52] that does run whatever you choose in docker...might be exactly what c.danis pulled up [13:01:15] I am still not sure what rake&helm are _doing_ that takes half an hour, but eh [13:01:44] I would assume something goes completely south [13:02:26] thing is, I get the diff, helm lint works fine and I get diff and `END DEPLOYMENTS` [13:06:18] yeah. If I where to assume I'd say it blocks somewhere in the multithreading code [13:17:35] It's not spinning on CPU, so deadlock seems the most likely. Question is how do I figure out why it seems reproducible with this change.... hmmm, maybe if I split the changes out [14:28:37] has anyone played around with the default kubernetes dashboard? Coming from nomad where it's all built-in, I'm not loving it so far [14:29:37] If there's a better one LMK. I tried Octant, but it's not maintained [14:31:16] yeah rake run_locally is where I got my command [14:33:16] Splitting my change into commits has let me find odd bugs (where the old and new netyworPolicy synatx differs), and linitng now completes, both locally and on CI \o/ [14:33:38] {◕ ◡ ◕} [14:34:27] Question now is, do I split this up into a series of dependent patches for review so I can try them a step at a time in prod, or would that annoy the reviewer(s) too much... [14:34:44] Sometimes I wish we had something like Rosie... [14:47:08] what's Rosie? [14:50:55] It's a tool at Google that lets you split up repo-wide monster CLs that touch everybody's code into smaller chunks, for individual review and submission