Include more test schedules in valgrind testing #216
Valgrind job could use detached test structure so that we wouldn't need to have 2 jobs and things would be more clean.
This wasn't trivial so we decided to merge the working PR as is.
Integrating into that detached test structure has several pieces, one of them was https://github.com/citusdata/test-automation/pull/203
Now we can remove tooling from tools repo (or we can deprecate it)
We should not push weekly results into different branches #170
We should put branch name/sha of the HEAD and pg version to the valgrind test results
We should collect stack traces from core dumps if any crash happens
Research github api to understand success of last valgrind test
Research ways to automate manual testing (maybe pushing branches and removing them automatically ?)
Copy & pasting the improvements from https://github.com/citusdata/test-automation/pull/188#issue-443901788, also adding a few more things: