-
Type: Task
-
Resolution: Unresolved
-
Priority: Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
Query Execution
-
QE 2025-01-20
-
200
while writing this test I encountered an issue where its hard to compare placement results when the db is implicitly created, we don't get to pick the shard it's created on. maybe setting it though a failpoint could help or adding an option to the test harness to not compare placement. when I commented out comparing placement all the tests passed so there probably isn't a bug related to it