Skip to content

[Digital Twins - Core] DigitalTwins Components - read, update and delete operations update component not existing failing in nightly runs #29768

Open

Description

Digital Twins - Core nightly test runs are failing with:

Stack trace:
AssertionError: expected '/Component2/ComponentProp1 was not fo…' to include 'Could not resolve path'
at Context. (test/public/testComponents.spec.ts:362:6 <- dist-test/index.browser.js:51414:24)

For more details check here:
https://dev.azure.com/azure-sdk/internal/_build/results?buildId=3803148&view=results

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.Digital Twinstest-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