Skip to content

Add .NET client for dynamic pubsub subscriptions #1617

Add .NET client for dynamic pubsub subscriptions

Add .NET client for dynamic pubsub subscriptions #1617

Triggered via pull request September 15, 2024 08:04
Status Failure
Total duration 1m 57s
Artifacts

itests.yml

on: pull_request
Matrix: run integration tests
Fit to window
Zoom out
Zoom in

Annotations

17 errors and 3 warnings
run integration tests (8.0): src/Dapr.Messaging/AssemblyInfo.cs#L16
Friend assembly reference 'Dapr.Messaging.Test' is invalid. Strong-name signed assemblies must specify a public key in their InternalsVisibleTo declarations.
run integration tests (8.0): src/Dapr.Messaging/AssemblyInfo.cs#L16
Friend assembly reference 'Dapr.Messaging.Test' is invalid. Strong-name signed assemblies must specify a public key in their InternalsVisibleTo declarations.
run integration tests (8.0): src/Dapr.Messaging/AssemblyInfo.cs#L16
Friend assembly reference 'Dapr.Messaging.Test' is invalid. Strong-name signed assemblies must specify a public key in their InternalsVisibleTo declarations.
run integration tests (8.0): src/Dapr.Messaging/AssemblyInfo.cs#L16
Friend assembly reference 'Dapr.Messaging.Test' is invalid. Strong-name signed assemblies must specify a public key in their InternalsVisibleTo declarations.
run integration tests (8.0)
Process completed with exit code 1.
run integration tests (7.0)
The job was canceled because "_8_0" failed.
run integration tests (7.0): src/Dapr.Messaging/AssemblyInfo.cs#L16
Friend assembly reference 'Dapr.Messaging.Test' is invalid. Strong-name signed assemblies must specify a public key in their InternalsVisibleTo declarations.
run integration tests (7.0): src/Dapr.Messaging/AssemblyInfo.cs#L16
Friend assembly reference 'Dapr.Messaging.Test' is invalid. Strong-name signed assemblies must specify a public key in their InternalsVisibleTo declarations.
run integration tests (7.0): src/Dapr.Messaging/AssemblyInfo.cs#L16
Friend assembly reference 'Dapr.Messaging.Test' is invalid. Strong-name signed assemblies must specify a public key in their InternalsVisibleTo declarations.
run integration tests (7.0): src/Dapr.Messaging/AssemblyInfo.cs#L16
Friend assembly reference 'Dapr.Messaging.Test' is invalid. Strong-name signed assemblies must specify a public key in their InternalsVisibleTo declarations.
run integration tests (7.0)
The operation was canceled.
run integration tests (6.0)
The job was canceled because "_8_0" failed.
run integration tests (6.0): src/Dapr.Messaging/AssemblyInfo.cs#L16
Friend assembly reference 'Dapr.Messaging.Test' is invalid. Strong-name signed assemblies must specify a public key in their InternalsVisibleTo declarations.
run integration tests (6.0): src/Dapr.Messaging/AssemblyInfo.cs#L16
Friend assembly reference 'Dapr.Messaging.Test' is invalid. Strong-name signed assemblies must specify a public key in their InternalsVisibleTo declarations.
run integration tests (6.0): src/Dapr.Messaging/AssemblyInfo.cs#L16
Friend assembly reference 'Dapr.Messaging.Test' is invalid. Strong-name signed assemblies must specify a public key in their InternalsVisibleTo declarations.
run integration tests (6.0): src/Dapr.Messaging/AssemblyInfo.cs#L16
Friend assembly reference 'Dapr.Messaging.Test' is invalid. Strong-name signed assemblies must specify a public key in their InternalsVisibleTo declarations.
run integration tests (6.0)
The operation was canceled.
run integration tests (8.0)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/setup-dotnet@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
run integration tests (8.0)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/setup-dotnet@v1. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
run integration tests (7.0)
.NET 7.0 is no longer supported and will not receive security updates in the future. Please refer to https://aka.ms/dotnet-core-support for more information about the .NET support policy.