-
Notifications
You must be signed in to change notification settings - Fork 82
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
Read sometimes not cached in functional tests. #212
Comments
If OCF encounters a read miss it:
The IO is completed at step 3, execution of test continues and assertion fails because step 4 wasn't executed yet. We gotta think of some way to wait for backfill or drop assertions which check each and every time if data that should be inserted is inserted. Maybe split it out to dedicated tests which make sure bf run, and don't bother with it in other tests? |
We plan to implement a utility to settle OCF to make sure there is no outstanding activity after I/O is completed. Initial version of this feature is available here: |
LOGS from pyocf
Test name: test_start_read_first_and_check_mode
I encountered this several times, however it is very sporadic. Seems like it isn't related to hardware configuration.
The text was updated successfully, but these errors were encountered: