Skip to content

[Schema Registry] SchemaRegistryClient fails to get schema ID when no matching schema exists failing in nightly runs #22088

Closed

Description

Schema Registry nightly test runs are failing with:

Error message:
expected 'TrackingId:ebfc41a8-a912-4f19-b31f-55…' to match /does not exist/

Stack trace:
AssertionError: expected 'TrackingId:ebfc41a8-a912-4f19-b31f-55…' to match /does not exist/
at isRejected (D:\a_work\1\s\sdk\schemaregistry\schema-registry\test\public\schemaRegistry.spec.ts:60:14)
at processTicksAndRejections (internal/process/task_queues.js:97:5)

For more details check here:

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Assignees

Labels

ClientThis issue points to a problem in the data-plane of the library.Schema Registrytest-reliabilityIssue that causes tests to be unreliable

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions