fix: remove flaky network-requests assertion from testVectorsDBStats

assertProjectRequestsAtLeastGlobal() compares the cumulative static
$globalRequestsTotal counter against the eventually-consistent
network.requests metric. The test's own just-issued vector
create/delete requests are the last to flush through usage
aggregation, so when the flush lags past the 10s poll window the
server reports one fewer request, producing the intermittent
"231 vs 232" lower-bound failure.

The invariant is unrelated to vector DB stats and is still asserted
in five other usage tests, so dropping it here removes the race
without losing coverage.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
This commit is contained in:
loks0nandClaude Opus 4.8 committed 2026-06-24 10:24:22 +01:00
1 parent fdc3e61b9c
commit 33a59268e8
1 file changed
-2
-2
View File
@@ -1466,8 +1466,6 @@ final class UsageTest extends Scope
$collectionsTotal = $data['vectordbCollectionsTotal'];
$documentsTotal = $data['vectordbDocumentsTotal'];
$this->assertProjectRequestsAtLeastGlobal();
// Project-wide scalars: vectorsdbDatabasesTotal counts ONLY VectorsDB instances
// (not relational databases), vectorsdbDocumentsTotal is the sum of all vector
// documents across this project. Both are produced exclusively by