Repository navigation
acc: split vector search tests between direct and DMS - #7176
Conversation
…MS variant The initial deploy spends ~20 min waiting for the endpoint and index on cloud, and DMS does not affect recreation, so the DMS=true variant doubled the nightly cost without adding coverage. Co-authored-by: Isaac <no-reply@databricks.com>
|
Commit: Regression test reportSelected 16 changed tests (limit=20, 0 not selected) 16 tests: regression=0 unreleased=0 coverage=16 failing=0
|
Co-authored-by: Isaac <no-reply@databricks.com>
Integration test reportCommit: 83227bc
Top 23 slowest tests (at least 2 minutes):
|
andrewnester
left a comment
There was a problem hiding this comment.
Do we have any vector search test that runs on DMS=true? If ot, we may run into a situation where backend rejects vector search resource but we don't have it covered (this is prompted by internal_immutable_snapshot resource not being handled by DMS)
good point - I'll split them 50/50 between direct and DMS. |
Co-authored-by: Isaac <no-reply@databricks.com>
Changes
Each vector search test now runs a single DMS variant instead of both:
EnvMatrix.DMS = [""]invector_search_indexes/test.tomlandvector_search_endpoints/test.toml, overridden to["true"]in 8 of the 16 tests. Of the 6 tests that run on cloud, 3 use each variant (endpoints:basicdirect,drift/recreated_same_nameDMS; indexes:basicandrecreate/embedding_dimensiondirect,grants/selectandschema_normalizationDMS).Why
Most of the cloud time in these tests is endpoint/index provisioning (e.g.
recreate/embedding_dimensionspends ~20-25 min on AWS/Azure in the initial deploy; the recreate itself takes ~10s). Running every test under both variants doubled that cost; splitting keeps both paths covered for each resource type.Tests
Regenerated
out.test.tomlfiles; all 16 pass locally against the testserver.This pull request and its description were written by Isaac.