Don't send out Runtime error telemetry when can't create LearningModelDevice on machine without hardware adapters #6535
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.
Runtime error telemetry should only be sent out for scenarios where WinML behaved in an unexpected incorrect way.
In the scenario, that there are no hardware adapters available and a LearningModelDevice targetting GPU can't be created, Runtime error telemetry shouldn't be sent but hresult error should still be returned to the client app.
TelemetryFallback callback function that calls LogRuntimeError for any failure can be removed for these reasons: