Commit 87ef5e2
authored
test: fix vector progress callback timing assertion (#6437)
This updates the vector progress-callback test to stop treating
`complete:merge_partitions` as if the full `create_index` operation has
already finished. That assumption is timing-dependent because the final
dataset commit happens after partition merge completes, which made the
test fail on Windows while the implementation was still behaving as
designed.
The revised test now checks a deterministic earlier failure point: if
the callback raises at `complete:shuffle`, `create_index` should
propagate the error and leave the dataset without a committed index.
Validation was limited to a local `python3 -m py_compile
python/python/tests/test_vector_index.py` syntax check; I did not run
the full Python test suite locally because building the editable
extension would require a longer Rust/Python release build.1 parent 83ae74b commit 87ef5e2
1 file changed
Lines changed: 13 additions & 12 deletions
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
219 | 219 | | |
220 | 220 | | |
221 | 221 | | |
222 | | - | |
| 222 | + | |
223 | 223 | | |
224 | 224 | | |
225 | 225 | | |
226 | | - | |
| 226 | + | |
227 | 227 | | |
228 | | - | |
229 | | - | |
230 | | - | |
231 | | - | |
232 | | - | |
233 | | - | |
234 | | - | |
| 228 | + | |
| 229 | + | |
| 230 | + | |
| 231 | + | |
| 232 | + | |
| 233 | + | |
| 234 | + | |
| 235 | + | |
235 | 236 | | |
236 | 237 | | |
237 | | - | |
238 | | - | |
239 | | - | |
| 238 | + | |
| 239 | + | |
| 240 | + | |
240 | 241 | | |
241 | 242 | | |
242 | 243 | | |
| |||
0 commit comments