* prepare a test for valgrind by fixing linter issues
* something went wrong
* Try update cereal
* Not working, fixing replay_learning.py
* Testing
* Testing
* Working now
* More logs, a bit of cleaning, still no idea how this works
* Ok got 10% cleaning done
* trying some stackOverflow code
* Lots of cleaning
* wip
* Delete valgrind_testing.py
* Delete replay_learning.py
* Add to CI, cannot fail though
* Add to CI, cannot fail though
* Now the unit test should fail
* Dump valgrind output in case of a failure
* fix subrepos
* fix subs
* hopefully fixes every issue that we have
* wait for message confirmation
* Revert "wait for message confirmation"
This reverts commit ad7ba280ec6536015ac1a442c9732bfe42fd5664.
* fix local issues
* Revert "fix local issues"
This reverts commit 4498df21df471fa6e9360d50407eaefdf24ae69f.
* attempt 3 to fix things
* untested function extraction
* refactor
* add valgrind task
* add delay and BASEDIR
* Make test not fail, it is not designed for that
* fix subrepositories
* fix tests
* Real fix now :)
* scons
* ... stupid CI
* fix valgrind CI
* Update test.yaml
* Update test.yaml
* Update test.yaml
* add valgrind logs as file
* remove delays
* kill process more reliably
* rename action
* small cleanup
* fix casting to int in case of large leaks
Co-authored-by: Willem Melching <willem.melching@gmail.com>
* kind of works
* move that
* hack to get camerad to reliably terminate
* not sure why SIGTERM wasn't working before
* compare bytes
* clean up some hacks
* gitignore
* fix that
* WIP
* no reboot
* comparison works
* pretty print
* fix build
* run in jenkins
* python path
* space
* raise timeout
* new eon
* skip the copy
* spinner
* spin less
* update model ref commit
* reenable that
* clean up
* fix jenkinsfile
* parallel
* wrap it in a stage
* fix linter
* better progress
* lower timeout
Co-authored-by: Comma Device <device@comma.ai>
Co-authored-by: Adeeb Shihadeh <adeebshihadeh@gmail.com>