Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Valgrind test improvements / Parent Issue #204

Open
onurctirtir opened this issue Feb 1, 2021 · 0 comments
Open

Valgrind test improvements / Parent Issue #204

onurctirtir opened this issue Feb 1, 2021 · 0 comments

Comments

@onurctirtir
Copy link
Member

onurctirtir commented Feb 1, 2021

Copy & pasting the improvements from #188 (comment), also adding a few more things:


  • Include more test schedules in valgrind testing 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 Cache git credentials in init.sh #203
  • Now we can remove tooling from tools repo (or we can deprecate it)
  • We should not push weekly results into different branches Valgrind test results should be pushed to a single branch #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 ?)
@onurctirtir onurctirtir changed the title Valgrind test improvements Valgrind test improvements / Parent Issue Feb 1, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant