Open
Bug 1846510
Opened 1 year ago
Updated 1 year ago
Improve IndexedDB idle maintenance testing
Categories
(Core :: Storage: IndexedDB, task, P3)
Core
Storage: IndexedDB
Tracking
()
NEW
People
(Reporter: jjalkanen, Assigned: jjalkanen)
References
Details
IndexedDB idle maintenance is tested in the test_idle_maintenance.js test by writing some data to a datastore, then removing it and sending a fake signal which should trigger the idle maintenance. The problems with this timing based test are that
- the write may not have started or is ongoing when the idle maintenance is triggered
- there's not enough data written that any maintenance is actually done
- the write or the maintenance may be ongoing when the expectations are checked at the end
It would be good to find a more robust way to test this feature, and cover
- the expected idle maintenance flow
- the cases when the maintenance gets interrupted by shutdown
- the case when maintenance is interrupted by IndexedDB requests
- the case when there are not enough threads
- database/disk hangs
and many more.
You need to log in
before you can comment on or make changes to this bug.
Description
•