-
Notifications
You must be signed in to change notification settings - Fork 4.7k
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
Comments
Tagging subscribers to this area: @dotnet/area-infrastructure-libraries |
Tagging subscribers to this area: @dotnet/ncl |
This failure on Browser is already tracked by #71877. The test in question should already be disabled there: runtime/src/libraries/System.Net.Http/tests/FunctionalTests/TelemetryTest.cs Lines 24 to 31 in f87687a
Does |
Maybe on browser the env variable |
@ilonatommy this and #105363 are getting hit a lot. please take a look |
The test is run with It's true that
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:
set by this stub: runtime/src/libraries/Common/tests/TestUtilities/ILLink.Substitutions.AggressiveTrimming.xml Line 4 in edaa25e
from here:
I will add appropriate blocking condition in a PR soon. |
About this part:
I found where we're setting it:
that triggers: runtime/src/mono/browser/runtime/runtime.c Lines 308 to 312 in 8e8143e
so the existing blocker is also fine. |
Browser does not support diagnostics, so in the current state it's expected to trim
This can be enabled once we have EP working on WASM browser. |
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.
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
The text was updated successfully, but these errors were encountered: