Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

System.Net.Http.Functional.Tests.TelemetryTest failing with differing string #109024

Open
tannergooding opened this issue Oct 18, 2024 · 8 comments
Assignees
Labels
area-System.Net.Http disabled-test The test is disabled in source code against the issue Known Build Error Use this to report build issues in the .NET Helix tab os-browser Browser variant of arch-wasm
Milestone

Comments

@tannergooding
Copy link
Member

tannergooding commented Oct 18, 2024

Build Information

Build: https://dev.azure.com/dnceng-public/public/_build/results?buildId=847502
Build error leg or test failing: EventSource_ExistsWithCorrectId

Error Message

Fill the error message using step by step known issues guidance.

{
  "ErrorMessage": ["Expected: \"System.Net.Http\"", "Actual:   \"HttpTelemetry\""],
  "BuildRetry": false,
  "ExcludeConsoleLog": false
}

Known issue validation

Build: 🔎 https://dev.azure.com/dnceng-public/public/_build/results?buildId=847502
Error message validated: [Expected: "System.Net.Http" Actual: "HttpTelemetry"]
Result validation: ✅ Known issue matched with the provided build.
Validation performed at: 10/18/2024 7:25:09 PM UTC

Report

Summary

24-Hour Hit Count 7-Day Hit Count 1-Month Count
0 0 0
@tannergooding tannergooding added the Known Build Error Use this to report build issues in the .NET Helix tab label Oct 18, 2024
@dotnet-policy-service dotnet-policy-service bot added the untriaged New issue has not been triaged by the area owner label Oct 18, 2024
Copy link
Contributor

Tagging subscribers to this area: @dotnet/area-infrastructure-libraries
See info in area-owners.md if you want to be subscribed.

Copy link
Contributor

Tagging subscribers to this area: @dotnet/ncl
See info in area-owners.md if you want to be subscribed.

@MihaZupan MihaZupan added the os-browser Browser variant of arch-wasm label Oct 21, 2024
@MihaZupan
Copy link
Member

This failure on Browser is already tracked by #71877. The test in question should already be disabled there:

[Fact]
[ActiveIssue("https://github.com/dotnet/runtime/issues/71877", typeof(PlatformDetection), nameof(PlatformDetection.IsBrowser), nameof(PlatformDetection.IsMonoAOT))]
public void EventSource_ExistsWithCorrectId()
{
Type esType = typeof(HttpClient).Assembly.GetType("System.Net.Http.HttpTelemetry", throwOnError: true, ignoreCase: false);
Assert.NotNull(esType);
Assert.Equal("System.Net.Http", EventSource.GetName(esType));

Does WasmTestOnChrome not fall under PlatformDetection.IsBrowser?

@pavelsavara
Copy link
Member

Maybe on browser the env variable MONO_AOT_MODE is never set ?

@pavelsavara pavelsavara added the blocking-clean-ci Blocking PR or rolling runs of 'runtime' or 'runtime-extra-platforms' label Oct 22, 2024
@lewing
Copy link
Member

lewing commented Oct 23, 2024

@ilonatommy this and #105363 are getting hit a lot. please take a look

@ilonatommy
Copy link
Member

Maybe on browser the env variable MONO_AOT_MODE is never set ?

The test is run with /p:EnableAggressiveTrimming=true /p:BuildAOTTestsOnHelix=true /p:RunAOTCompilation=false.

It's true that MONO_AOT_MODE is never set, because ENABLE_AOT is not defined. I guess it should be set here:


The tests, however fail when AOT = false, so the active issue does not prevent it. We have a detection for EAT on wasm browser, it's this property:
public static bool IsBuiltWithAggressiveTrimming => IsNativeAot || IsAppleMobile;

set by this stub:
<method signature="System.Boolean get_IsBuiltWithAggressiveTrimming()" body="stub" value="true" />

from here:
<EmbeddedResource Include="$(MSBuildThisFileDirectory)ILLink.Substitutions.AggressiveTrimming.xml"

I will add appropriate blocking condition in a PR soon.

@ilonatommy
Copy link
Member

ilonatommy commented Oct 24, 2024

About this part:

Maybe on browser the env variable MONO_AOT_MODE is never set ?

It's true that MONO_AOT_MODE is never set, because ENABLE_AOT is not defined.

I found where we're setting it:

<_EmccCFlags Include="-DENABLE_AOT=1" Condition="'$(_WasmShouldAOT)' == 'true'" />

that triggers:

#ifdef ENABLE_AOT
monoeg_g_setenv ("MONO_AOT_MODE", "aot", 1);
// Defined in driver-gen.c
register_aot_modules ();

so the existing blocker is also fine.

@ilonatommy
Copy link
Member

Browser does not support diagnostics, so in the current state it's expected to trim

[EventSource(Name = "System.Net.Http")]

This can be enabled once we have EP working on WASM browser.

@MihaZupan MihaZupan added disabled-test The test is disabled in source code against the issue and removed untriaged New issue has not been triaged by the area owner labels Oct 24, 2024
@MihaZupan MihaZupan added this to the Future milestone Oct 24, 2024
@MihaZupan MihaZupan removed the blocking-clean-ci Blocking PR or rolling runs of 'runtime' or 'runtime-extra-platforms' label Oct 24, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area-System.Net.Http disabled-test The test is disabled in source code against the issue Known Build Error Use this to report build issues in the .NET Helix tab os-browser Browser variant of arch-wasm
Projects
None yet
Development

No branches or pull requests

6 participants