arcade: Signtool telemetry fails for Linux files in release pipeline

This issue is blocking
This issue is causing unreasonable pain

Signtool telemetry errors after signing linux files in release pipeline.

This is the error


D:\workspace\_work\1\s\src\Microsoft.DotNet.Release\Microsoft.DotNet.Signing.Extensions\SignLinuxPackages.proj(37,9): error MSB4018: The "Microsoft.DotNet.SignTool.SignToolTask" task failed unexpectedly.
D:\workspace\_work\1\s\src\Microsoft.DotNet.Release\Microsoft.DotNet.Signing.Extensions\SignLinuxPackages.proj(37,9): error MSB4018: System.TypeInitializationException: The type initializer for 'Microsoft.ApplicationInsights.Extensibility.Implementation.Tracing.CoreEventSource' threw an exception.
D:\workspace\_work\1\s\src\Microsoft.DotNet.Release\Microsoft.DotNet.Signing.Extensions\SignLinuxPackages.proj(37,9): error MSB4018:  ---> System.NullReferenceException: Object reference not set to an instance of an object.
D:\workspace\_work\1\s\src\Microsoft.DotNet.Release\Microsoft.DotNet.Signing.Extensions\SignLinuxPackages.proj(37,9): error MSB4018:    at System.Diagnostics.Tracing.CounterGroup.OnEventSourceCommand(Object sender, EventCommandEventArgs e)
D:\workspace\_work\1\s\src\Microsoft.DotNet.Release\Microsoft.DotNet.Signing.Extensions\SignLinuxPackages.proj(37,9): error MSB4018:    at System.Diagnostics.Tracing.EventSource.add_EventCommandExecuted(EventHandler`1 value)
D:\workspace\_work\1\s\src\Microsoft.DotNet.Release\Microsoft.DotNet.Signing.Extensions\SignLinuxPackages.proj(37,9): error MSB4018:    at System.Diagnostics.Tracing.CounterGroup.RegisterCommandCallback()
D:\workspace\_work\1\s\src\Microsoft.DotNet.Release\Microsoft.DotNet.Signing.Extensions\SignLinuxPackages.proj(37,9): error MSB4018:    at System.Diagnostics.Tracing.CounterGroup..ctor(EventSource eventSource)
D:\workspace\_work\1\s\src\Microsoft.DotNet.Release\Microsoft.DotNet.Signing.Extensions\SignLinuxPackages.proj(37,9): error MSB4018:    at System.Diagnostics.Tracing.CounterGroup.GetCounterGroup(EventSource eventSource)
D:\workspace\_work\1\s\src\Microsoft.DotNet.Release\Microsoft.DotNet.Signing.Extensions\SignLinuxPackages.proj(37,9): error MSB4018:    at System.Diagnostics.Tracing.DiagnosticCounter.Publish()
D:\workspace\_work\1\s\src\Microsoft.DotNet.Release\Microsoft.DotNet.Signing.Extensions\SignLinuxPackages.proj(37,9): error MSB4018:    at System.Diagnostics.Tracing.EventCounter..ctor(String name, EventSource eventSource)
D:\workspace\_work\1\s\src\Microsoft.DotNet.Release\Microsoft.DotNet.Signing.Extensions\SignLinuxPackages.proj(37,9): error MSB4018:    at Microsoft.ApplicationInsights.Extensibility.Implementation.Tracing.CoreEventSource..ctor()
D:\workspace\_work\1\s\src\Microsoft.DotNet.Release\Microsoft.DotNet.Signing.Extensions\SignLinuxPackages.proj(37,9): error MSB4018:    at Microsoft.ApplicationInsights.Extensibility.Implementation.Tracing.CoreEventSource..cctor()
D:\workspace\_work\1\s\src\Microsoft.DotNet.Release\Microsoft.DotNet.Signing.Extensions\SignLinuxPackages.proj(37,9): error MSB4018:    --- End of inner exception stack trace ---
D:\workspace\_work\1\s\src\Microsoft.DotNet.Release\Microsoft.DotNet.Signing.Extensions\SignLinuxPackages.proj(37,9): error MSB4018:    at Microsoft.ApplicationInsights.Extensibility.Implementation.Tracing.CoreEventSource.get_IsVerboseEnabled()
D:\workspace\_work\1\s\src\Microsoft.DotNet.Release\Microsoft.DotNet.Signing.Extensions\SignLinuxPackages.proj(37,9): error MSB4018:    at Microsoft.ApplicationInsights.Channel.InMemoryChannel.Send(ITelemetry item)
D:\workspace\_work\1\s\src\Microsoft.DotNet.Release\Microsoft.DotNet.Signing.Extensions\SignLinuxPackages.proj(37,9): error MSB4018:    at Microsoft.ApplicationInsights.Extensibility.Implementation.TransmissionProcessor.Process(ITelemetry item)
D:\workspace\_work\1\s\src\Microsoft.DotNet.Release\Microsoft.DotNet.Signing.Extensions\SignLinuxPackages.proj(37,9): error MSB4018:    at Microsoft.ApplicationInsights.Extensibility.Implementation.TelemetryProcessorChain.Process(ITelemetry item)
D:\workspace\_work\1\s\src\Microsoft.DotNet.Release\Microsoft.DotNet.Signing.Extensions\SignLinuxPackages.proj(37,9): error MSB4018:    at Microsoft.ApplicationInsights.Extensibility.TelemetrySink.Process(ITelemetry item)
D:\workspace\_work\1\s\src\Microsoft.DotNet.Release\Microsoft.DotNet.Signing.Extensions\SignLinuxPackages.proj(37,9): error MSB4018:    at Microsoft.ApplicationInsights.Shared.Extensibility.Implementation.PassThroughProcessor.Process(ITelemetry item)
D:\workspace\_work\1\s\src\Microsoft.DotNet.Release\Microsoft.DotNet.Signing.Extensions\SignLinuxPackages.proj(37,9): error MSB4018:    at Microsoft.ApplicationInsights.Extensibility.Implementation.TelemetryProcessorChain.Process(ITelemetry item)
D:\workspace\_work\1\s\src\Microsoft.DotNet.Release\Microsoft.DotNet.Signing.Extensions\SignLinuxPackages.proj(37,9): error MSB4018:    at Microsoft.ApplicationInsights.TelemetryClient.Track(ITelemetry telemetry)
D:\workspace\_work\1\s\src\Microsoft.DotNet.Release\Microsoft.DotNet.Signing.Extensions\SignLinuxPackages.proj(37,9): error MSB4018:    at Microsoft.ApplicationInsights.TelemetryClient.TrackEvent(EventTelemetry telemetry)
D:\workspace\_work\1\s\src\Microsoft.DotNet.Release\Microsoft.DotNet.Signing.Extensions\SignLinuxPackages.proj(37,9): error MSB4018:    at Microsoft.ApplicationInsights.TelemetryClient.TrackEvent(String eventName, IDictionary`2 properties, IDictionary`2 metrics)
D:\workspace\_work\1\s\src\Microsoft.DotNet.Release\Microsoft.DotNet.Signing.Extensions\SignLinuxPackages.proj(37,9): error MSB4018:    at Microsoft.DotNet.SignTool.Telemetry.SendEvents() in /_/src/Microsoft.DotNet.SignTool/src/Telemetry.cs:line 40
D:\workspace\_work\1\s\src\Microsoft.DotNet.Release\Microsoft.DotNet.Signing.Extensions\SignLinuxPackages.proj(37,9): error MSB4018:    at Microsoft.DotNet.SignTool.SignToolTask.ExecuteImpl() in /_/src/Microsoft.DotNet.SignTool/src/SignToolTask.cs:line 266
D:\workspace\_work\1\s\src\Microsoft.DotNet.Release\Microsoft.DotNet.Signing.Extensions\SignLinuxPackages.proj(37,9): error MSB4018:    at Microsoft.DotNet.SignTool.SignToolTask.Execute() in /_/src/Microsoft.DotNet.SignTool/src/SignToolTask.cs:line 154
D:\workspace\_work\1\s\src\Microsoft.DotNet.Release\Microsoft.DotNet.Signing.Extensions\SignLinuxPackages.proj(37,9): error MSB4018:    at Microsoft.Build.BackEnd.TaskExecutionHost.Microsoft.Build.BackEnd.ITaskExecutionHost.Execute()
D:\workspace\_work\1\s\src\Microsoft.DotNet.Release\Microsoft.DotNet.Signing.Extensions\SignLinuxPackages.proj(37,9): error MSB4018: --- End of stack trace from previous location ---

this is sample build -> https://dev.azure.com/dnceng/internal/_build/results?buildId=1227813&view=logs&j=d7f318d2-3658-5f56-29df-16b211ec56a6&t=7851342b-b7f6-561e-0dbe-e63708dfa83e

Versions :

SignToolVersion : 6.0.0-beta.21357.3 FeedsTaskVersion : 6.0.0-beta.21357.3

cc: @adiaaida @jonfortescue @markwilkie @chcosta

About this issue

Original URL
State: open
Created 3 years ago
Comments: 16 (16 by maintainers)

Most upvoted comments

Yes I followed up and created an issue in application insights -https://github.com/microsoft/ApplicationInsights-dotnet/issues/2323 no response yet.

epananth on Jul 15, 2021

Agreed. I mentioned that in previous discussions, and also that it’s unclear when / if it will be fixed. The quirk being that the appinsights issue is specifically related to core, but sign tool runs on framework. Here was my comment around that…

[6/30/2021 1:32 PM] Christopher Costa I think you’re hitting a bug in appinsights. TypeInitializationException thrown for trimmed applications (worked in beta2 and prior) · Issue #2058 · microsoft/ApplicationInsights-dotnet (github.com) or something similar

[6/30/2021 1:33 PM] Christopher Costa i’m not certain if it’s the exact same bug, you might need to file a new issue

I mention that if only to say that the important thing is the last thing I wrote. We should make sure we’re communicating with the app insights team about this and at least relaying our scenario (framework). It would be disappointing if they decided to finally fix this but only for core and we remain broken even longer than necessary. They might also say “no, that’s something else”. Which is a fine response.

chcosta on Jul 15, 2021