Files
dragonpilot/selfdrive/test/process_replay
Willem Melching d3d10e014a Ensure controlsd can engage again in process replay (#23556)
* hacks to make process replay engage again

* dont change that

* enable engagement check again

* chmod +x

* first working regen

* proper logMonoTime

* fix video framerate consistency

* mpc is valid again

* proper alive checks

* revert loggerd change

* ensure engaged in regen, fix managerState, peripheralState

* ubloxRaw is unused

* add submaster config for gm

* regen all services we can run without HW

* fix loggerd

* loggerd: matroska without the extension

* update ref
2022-01-21 13:13:34 +01:00
..
2020-01-17 11:16:14 -08:00
2021-06-28 21:44:40 -07:00
2021-05-06 19:27:58 +02:00

process replay

Process replay is a regression test designed to identify any changes in the output of a process. This test replays a segment through individual processes and compares the output to a known good replay. Each make is represented in the test with a segment.

If the test fails, make sure that you didn't unintentionally change anything. If there are intentional changes, the reference logs will be updated.

Use test_processes.py to run the test locally.

Currently the following processes are tested:

  • controlsd
  • radard
  • plannerd
  • calibrationd
  • ubloxd

Forks

openpilot forks can use this test with their own reference logs

To generate new logs:

./update_refs.py --no-upload

Then, check in the new logs using git-lfs. Make sure to also include the updated ref_commit file.