release-20.1: server: Resolve default engine type in testserver #49377
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.
Previously we weren't resolving the engine type if it was
set to EngineTypeDefault in the testserver. This would silently
resolve to RocksDB (and in 20.2, pebble) anyway, so it was
only a concern in sentry reports where it would show up as
default
. Sincecockroach demo
uses the test server andhas sentry reports enabled, that was an oversight.
Fixes #49368.
Release note (bug fix): Report engine type correctly in bug reports
when using
cockroach demo
.