Skip to content

Bump docker/build-push-action from 6.7.0 to 6.8.0 in the github-actions group #982

Bump docker/build-push-action from 6.7.0 to 6.8.0 in the github-actions group

Bump docker/build-push-action from 6.7.0 to 6.8.0 in the github-actions group #982

Triggered via pull request September 29, 2024 22:49
Status Failure
Total duration 40m 51s
Artifacts

test-linux.yml

on: pull_request
Fit to window
Zoom out
Zoom in

Annotations

12 errors and 14 warnings
azure-tests
Login failed with Error: Using auth-type: SERVICE_PRINCIPAL. Not all values are present. Ensure 'client-id' and 'tenant-id' are supplied.. Double check if the 'auth-type' is correct. Refer to https://github.com/Azure/login#readme for more information.
Elastic.Apm.Profiler.Managed.Tests.AdoNet.SqlCommandTests.CaptureAutoInstrumentedSpans(targetFramework: "net8.0"): test/profiler/Elastic.Apm.Profiler.Managed.Tests/AdoNet/SqlCommandTests.cs#L35
Docker.DotNet.DockerApiException : Docker API responded with status code=Conflict, response={"message":"container 11e0b61e3a53792d1b0c612135d11ae128586d8d8bad4e2bf00f090073954117 is not running"}
Elastic.Apm.Profiler.Managed.Tests.AdoNet.SqlCommandTests.CaptureAutoInstrumentedSpans(targetFramework: "net6.0"): test/profiler/Elastic.Apm.Profiler.Managed.Tests/AdoNet/SqlCommandTests.cs#L35
Docker.DotNet.DockerApiException : Docker API responded with status code=Conflict, response={"message":"container 11e0b61e3a53792d1b0c612135d11ae128586d8d8bad4e2bf00f090073954117 is not running"}
profiler-tests
Process completed with exit code 1.
Elastic.Apm.SqlClient.Tests.EfCoreWithMsSqlTests.BothEfCoreAndSqlClientCapturingActive: test/instrumentations/Elastic.Apm.SqlClient.Tests/EfCoreWithMsSqlTests.cs#L49
Docker.DotNet.DockerApiException : Docker API responded with status code=Conflict, response={"message":"container 9dc9c31c42b73819cd77e1c0654992936894d62d520a956e0d16ec44256cbdf1 is not running"}
Elastic.Apm.SqlClient.Tests.SqlClientListenerTests.SqlClientDiagnosticListener_ShouldCaptureSpan: test/instrumentations/Elastic.Apm.SqlClient.Tests/SqlClientListenerTests.cs#L74
Docker.DotNet.DockerApiException : Docker API responded with status code=Conflict, response={"message":"container 9dc9c31c42b73819cd77e1c0654992936894d62d520a956e0d16ec44256cbdf1 is not running"}
Elastic.Apm.SqlClient.Tests.SqlClientListenerTests.SqlClientDiagnosticListener_ShouldCaptureSpan: test/instrumentations/Elastic.Apm.SqlClient.Tests/SqlClientListenerTests.cs#L74
Docker.DotNet.DockerApiException : Docker API responded with status code=Conflict, response={"message":"container 9dc9c31c42b73819cd77e1c0654992936894d62d520a956e0d16ec44256cbdf1 is not running"}
Elastic.Apm.SqlClient.Tests.SqlClientListenerTests.SqlClientDiagnosticListener_ShouldNotUseCumulativeDurations: test/instrumentations/Elastic.Apm.SqlClient.Tests/SqlClientListenerTests.cs#L192
Docker.DotNet.DockerApiException : Docker API responded with status code=Conflict, response={"message":"container 9dc9c31c42b73819cd77e1c0654992936894d62d520a956e0d16ec44256cbdf1 is not running"}
Elastic.Apm.SqlClient.Tests.SqlClientListenerTests.SqlClientDiagnosticListener_ShouldNotUseCumulativeDurations: test/instrumentations/Elastic.Apm.SqlClient.Tests/SqlClientListenerTests.cs#L192
Docker.DotNet.DockerApiException : Docker API responded with status code=Conflict, response={"message":"container 9dc9c31c42b73819cd77e1c0654992936894d62d520a956e0d16ec44256cbdf1 is not running"}
Elastic.Apm.SqlClient.Tests.SqlClientListenerTests.SqlClientDiagnosticListener_ShouldCaptureErrorFromSystemSqlClient: test/instrumentations/Elastic.Apm.SqlClient.Tests/SqlClientListenerTests.cs#L130
Docker.DotNet.DockerApiException : Docker API responded with status code=Conflict, response={"message":"container 9dc9c31c42b73819cd77e1c0654992936894d62d520a956e0d16ec44256cbdf1 is not running"}
Elastic.Apm.SqlClient.Tests.SqlClientListenerTests.SqlClientDiagnosticListener_ShouldCaptureErrorFromSystemSqlClient: test/instrumentations/Elastic.Apm.SqlClient.Tests/SqlClientListenerTests.cs#L130
Docker.DotNet.DockerApiException : Docker API responded with status code=Conflict, response={"message":"container 9dc9c31c42b73819cd77e1c0654992936894d62d520a956e0d16ec44256cbdf1 is not running"}
integration-tests
Process completed with exit code 1.
pack
New version for cargo-make available: 0.37.18
pack
Found version-specific or distribution-specific runtime identifier(s): win7-x64. Affected libraries: Microsoft.Azure.DocumentDB.Core. In .NET 8.0 and higher, assets for version-specific and distribution-specific runtime identifiers will not be found by default. See https://aka.ms/dotnet/rid-usage for details.
pack
Found version-specific or distribution-specific runtime identifier(s): win7-x64. Affected libraries: Microsoft.Azure.DocumentDB.Core. In .NET 8.0 and higher, assets for version-specific and distribution-specific runtime identifiers will not be found by default. See https://aka.ms/dotnet/rid-usage for details.
tests
Found version-specific or distribution-specific runtime identifier(s): win7-x64. Affected libraries: Microsoft.Azure.DocumentDB.Core. In .NET 8.0 and higher, assets for version-specific and distribution-specific runtime identifiers will not be found by default. See https://aka.ms/dotnet/rid-usage for details.
tests
Found version-specific or distribution-specific runtime identifier(s): win7-x64. Affected libraries: Microsoft.Azure.DocumentDB.Core. In .NET 8.0 and higher, assets for version-specific and distribution-specific runtime identifiers will not be found by default. See https://aka.ms/dotnet/rid-usage for details.
startup-hook-tests
Found version-specific or distribution-specific runtime identifier(s): win7-x64. Affected libraries: Microsoft.Azure.DocumentDB.Core. In .NET 8.0 and higher, assets for version-specific and distribution-specific runtime identifiers will not be found by default. See https://aka.ms/dotnet/rid-usage for details.
startup-hook-tests
Found version-specific or distribution-specific runtime identifier(s): win7-x64. Affected libraries: Microsoft.Azure.DocumentDB.Core. In .NET 8.0 and higher, assets for version-specific and distribution-specific runtime identifiers will not be found by default. See https://aka.ms/dotnet/rid-usage for details.
profiler-tests
New version for cargo-make available: 0.37.18
profiler-tests
Found version-specific or distribution-specific runtime identifier(s): win7-x64. Affected libraries: Microsoft.Azure.DocumentDB.Core. In .NET 8.0 and higher, assets for version-specific and distribution-specific runtime identifiers will not be found by default. See https://aka.ms/dotnet/rid-usage for details.
profiler-tests
Found version-specific or distribution-specific runtime identifier(s): win7-x64. Affected libraries: Microsoft.Azure.DocumentDB.Core. In .NET 8.0 and higher, assets for version-specific and distribution-specific runtime identifiers will not be found by default. See https://aka.ms/dotnet/rid-usage for details.
profiler-tests
Found version-specific or distribution-specific runtime identifier(s): win7-x64. Affected libraries: Microsoft.Azure.DocumentDB.Core. In .NET 8.0 and higher, assets for version-specific and distribution-specific runtime identifiers will not be found by default. See https://aka.ms/dotnet/rid-usage for details.
profiler-tests
Found version-specific or distribution-specific runtime identifier(s): win7-x64. Affected libraries: Microsoft.Azure.DocumentDB.Core. In .NET 8.0 and higher, assets for version-specific and distribution-specific runtime identifiers will not be found by default. See https://aka.ms/dotnet/rid-usage for details.
integration-tests
Found version-specific or distribution-specific runtime identifier(s): win7-x64. Affected libraries: Microsoft.Azure.DocumentDB.Core. In .NET 8.0 and higher, assets for version-specific and distribution-specific runtime identifiers will not be found by default. See https://aka.ms/dotnet/rid-usage for details.
integration-tests
Found version-specific or distribution-specific runtime identifier(s): win7-x64. Affected libraries: Microsoft.Azure.DocumentDB.Core. In .NET 8.0 and higher, assets for version-specific and distribution-specific runtime identifiers will not be found by default. See https://aka.ms/dotnet/rid-usage for details.