Repository navigation
Fail RavenDB tests that make a dynamic query create an auto index - #6115
Draft
mauroservienti wants to merge 2 commits into
Draft
mauroservienti wants to merge 2 commits into
mauroservienti wants to merge 2 commits into
Conversation
The check after each test covered only the error database in the persistence tests. It now also runs in the audit persistence tests and in the primary, audit, and multi-instance acceptance tests, for every database they use.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Before merging
master. Until then, the licensing tests fail here on the auto indexes Query the throughput endpoints through a static index #6099 removes.Description
A dynamic query makes RavenDB create an auto index. An auto index has no per-index search engine setting, so the search engine custom check keeps reporting it after all static indexes use Lucene. #6100 added a check after each test that fails it when the error database has an auto index, but only in
ServiceControl.Persistence.Tests.RavenDB. The queries made by the API, the background services, and the custom checks run in the acceptance tests, and the audit database was not checked anywhere.Changes
TestHelper.AutoIndexes: lists theAuto/indexes of the given databases, and treats a database that does not exist as having none.AssertNonefails the test with the database and index names.ServiceControl.Persistence.Tests.RavenDBServiceControl.Audit.Persistence.Tests.RavenDBServiceControl.AcceptanceTests.RavenDBServiceControl.Audit.AcceptanceTests.RavenDBServiceControl.MultiInstance.AcceptanceTestsIndexing.DisableQueryOptimizerGeneratedIndexeswould make a dynamic query throw where it runs, but the background services and custom checks catch and log exceptions, so a test would still pass. Checking for the auto indexes after the test catches every query that ran.What it finds
On
master:Auto/EndpointDocuments/ByEndpointId.ThroughputSource.With #6099 merged, all of these pass. The remaining local failures are the known setup failures with a refused connection to the shared embedded server on port 33334.