Skip to content

chore(deps): update dependency cognitesdk to 4.6.0 #1802

chore(deps): update dependency cognitesdk to 4.6.0

chore(deps): update dependency cognitesdk to 4.6.0 #1802

Triggered via pull request September 4, 2024 08:38
Status Failure
Total duration 1m 1s
Artifacts

build-and-test.yml

on: pull_request
Fit to window
Zoom out
Zoom in

Annotations

10 errors and 4 warnings
build: ExtractorUtils.Test/unit/BinaryBufferTest.cs#L32
'StatusCodeCategory' is an ambiguous reference between 'CogniteSdk.StatusCodeCategory' and 'Cognite.Extensions.StatusCodeCategory'
build: ExtractorUtils.Test/unit/BinaryBufferTest.cs#L33
'StatusCodeCategory' is an ambiguous reference between 'CogniteSdk.StatusCodeCategory' and 'Cognite.Extensions.StatusCodeCategory'
build: ExtractorUtils.Test/DataModelTestFixture.cs#L114
'InstanceIdentifier' does not contain a constructor that takes 3 arguments
build: ExtractorUtils.Test/DataModelTestFixture.cs#L151
'InstanceIdentifier' does not contain a constructor that takes 3 arguments
build: ExtractorUtils.Test/unit/SanitationTest.cs#L972
'StatusCodeCategory' is an ambiguous reference between 'CogniteSdk.StatusCodeCategory' and 'Cognite.Extensions.StatusCodeCategory'
build: ExtractorUtils.Test/unit/BinaryBufferTest.cs#L32
'StatusCodeCategory' is an ambiguous reference between 'CogniteSdk.StatusCodeCategory' and 'Cognite.Extensions.StatusCodeCategory'
build: ExtractorUtils.Test/unit/BinaryBufferTest.cs#L33
'StatusCodeCategory' is an ambiguous reference between 'CogniteSdk.StatusCodeCategory' and 'Cognite.Extensions.StatusCodeCategory'
build: ExtractorUtils.Test/DataModelTestFixture.cs#L114
'InstanceIdentifier' does not contain a constructor that takes 3 arguments
build: ExtractorUtils.Test/DataModelTestFixture.cs#L151
'InstanceIdentifier' does not contain a constructor that takes 3 arguments
build: ExtractorUtils.Test/unit/SanitationTest.cs#L972
'StatusCodeCategory' is an ambiguous reference between 'CogniteSdk.StatusCodeCategory' and 'Cognite.Extensions.StatusCodeCategory'
build: ExtractorUtils.Test/unit/DatapointsTest.cs#L95
Do not use Assert.Empty() to check if a value does not exist in a collection. Use Assert.DoesNotContain() instead. (https://xunit.net/xunit.analyzers/rules/xUnit2029)
build: ExtractorUtils.Test/unit/DatapointsTest.cs#L98
Do not use Assert.Empty() to check if a value does not exist in a collection. Use Assert.DoesNotContain() instead. (https://xunit.net/xunit.analyzers/rules/xUnit2029)
build: ExtractorUtils.Test/unit/DatapointsTest.cs#L95
Do not use Assert.Empty() to check if a value does not exist in a collection. Use Assert.DoesNotContain() instead. (https://xunit.net/xunit.analyzers/rules/xUnit2029)
build: ExtractorUtils.Test/unit/DatapointsTest.cs#L98
Do not use Assert.Empty() to check if a value does not exist in a collection. Use Assert.DoesNotContain() instead. (https://xunit.net/xunit.analyzers/rules/xUnit2029)