-
Type:
Bug
-
Resolution: Fixed
-
Priority:
Major - P3
-
Affects Version/s: None
-
Component/s: Test Csuite
-
None
-
Storage Engines, Storage Engines - Foundations
-
SE Foundations - 2025-08-01, SE Foundations - 2025-07-18
-
3
As part of the changes in WT-13310, several function names related to random number initialisation were updated (in rand.c). While it was correct to replace some instances of __wt_random_init with __wt_random_init_default, it appears that __wt_random_init_seed was also mistakenly replaced with __wt_random_init_default in certain places.
This leads to an issue, __wt_random_init_default uses a constant seed, which means we’re now generating predictable and identical random sequences in areas where randomness and variability were expected.
Action Items:
- Audit changes from
WT-13310involving random initialisation functions. - Revert or correct instances where __wt_random_init_seed was mistakenly replaced.
- Ensure the proper function is used:
- Use __wt_random_init_default only when a constant seed is desired.
- Use __wt_random_init_seed when test variability is required.
- is caused by
-
WT-13310 WT random cursor continues to return duplicate records due to poor interaction with MongoDB layer's query yielding
-
- Closed
-
- is related to
-
WT-13310 WT random cursor continues to return duplicate records due to poor interaction with MongoDB layer's query yielding
-
- Closed
-
-
WT-15049 Live-lock in eviction due to incorrect update chain iteration
-
- Closed
-
-
WT-15052 Disable rollback-to-stable and prepare operations in test/format for disagg
-
- Closed
-
-
WT-15028 Configure hook disagg python file to create layered tables through table: prefix
-
- Closed
-
- related to
-
WT-14034 Fix resolving the prepared key multiple times because of reserved updates
-
- Closed
-