Skip to content

Implement TableServiceClient #205

Implement TableServiceClient

Implement TableServiceClient #205

Triggered via pull request August 19, 2024 20:24
Status Failure
Total duration 33s
Artifacts

ci-build.yml

on: pull_request
build-core
22s
build-core
Fit to window
Zoom out
Zoom in

Annotations

7 errors and 2 warnings
build-core: CoreHelpers.WindowsAzure.Storage.Table/StorageContextTableManagement.cs#L110
The name '_connectionString' does not exist in the current context
build-core: CoreHelpers.WindowsAzure.Storage.Table/StorageContextTableManagement.cs#L110
The name '_connectionString' does not exist in the current context
build-core: CoreHelpers.WindowsAzure.Storage.Table/StorageContextTableManagement.cs#L110
The name '_connectionString' does not exist in the current context
build-core: CoreHelpers.WindowsAzure.Storage.Table/StorageContextTableManagement.cs#L110
The name '_connectionString' does not exist in the current context
build-core: CoreHelpers.WindowsAzure.Storage.Table/StorageContextTableManagement.cs#L110
The name '_connectionString' does not exist in the current context
build-core: CoreHelpers.WindowsAzure.Storage.Table/StorageContextTableManagement.cs#L110
The name '_connectionString' does not exist in the current context
build-core
Process completed with exit code 1.
build-core
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, 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/
build-core
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v2, 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/