-
Notifications
You must be signed in to change notification settings - Fork 9.5k
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
FW query timing test: mock get_data function for timeout #29712
Conversation
I want to start testing the full fingerprinting stack in openpilot, using commaai/panda#1329, which probably requires the original timeouts. Once I get that merged we look into this? I think the other test in this file also takes longer. |
Okay. Test also is inconsistent locally, okay if I bump up the tolerance? |
Closing this until we can test full panda stack |
The individual brands should be fairly consistent, it's the total time that is easy to deviate from the tolerance. |
while thread.is_alive(): | ||
time.sleep(0.02) | ||
time.sleep(0.001) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can you see if the change in timings for OBD multiplexing matches what it is when fingerprinting on device (think going onroad on a desk is enough)?
revert refs
This reverts commit 7a1d6a6.
)" This reverts commit 4028cb6.
rather than actually timing out, use a mock function to simulate the timeout to speed up the tests
@sshane any problem with using a mock function there? saves a bit of time in CI and will also be more consistent. it was failing in pytest sometimes: #29709
takes about 30 seconds as is, which makes sense as we run 5x, each with a 6s timeout
30.61s call selfdrive/car/tests/test_fw_fingerprint.py::TestFwFingerprintTiming::test_fw_query_timing