-
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
Test failure System.Tests.TimeZoneInfoTests.NJulianRuleTest(posixRule: \"<+00>0<+01>,A/0,J365/25\", dayNumber: 0, monthNumber: 0, shouldSucceed: False) #72825
Comments
I couldn't figure out the best area label to add to this issue. If you have write-permissions please help me learn by adding exactly one area label. |
Tagging subscribers to this area: @dotnet/area-system-runtime Issue DetailsRun: runtime-coreclr libraries-jitstressregs 20220725.1 Failed test:
Error message:
|
due to assertion failure:
guess: the tzfile on this configuration is slightly wrong, and this just happens to be using chk bits including a chk glibc? |
cc @tarekgh |
Tagging subscribers to this area: @dotnet/area-system-globalization Issue DetailsRun: runtime-coreclr libraries-jitstressregs 20220725.1 Failed test:
Error message:
|
Tagging subscribers to this area: @JulieLeeMSFT, @jakobbotsch Issue DetailsRun: runtime-coreclr libraries-jitstressregs 20220725.1 Failed test:
Error message:
|
For sure it is using the chk build of glibc. I am not sure if this is intended. Would be good if someone can confirm. In same time, I am seeing the assert is fired from https://sources.debian.org/src/glibc/2.28-10/time/tzfile.c/#L440. I'll try to look if I can modify the tz file we generate to avoid this assert. |
@BruceForstall is it expected that you use the chk glibc in these runs -- I assume so, because you want asserts for memory misuse, etc. |
Tagging subscribers to this area: @dotnet/area-system-runtime Issue DetailsRun: runtime-coreclr libraries-jitstressregs 20220725.1 Failed test:
Error message:
|
@VincentBu you have logged the failure with the pipelines runtime-coreclr libraries-jitstressregs 20220725.1 but when looking at the PR #72522 I am not seeing this pipeline in the CI run. Any idea about that? |
I am not sure. I just check the pipeline runtime-coreclr libraries-jitstressregs. There are 2 failed runs this months, the one is runtime-coreclr libraries-jitstressregs 20220725.1 and the other is runtime-coreclr libraries-jitstressregs 20220724.1. According to the summary of 20220724.1, it has nothing to do with #72522 |
/azp run runtime-coreclr jitstress edit: doh |
Run: runtime-coreclr libraries-jitstressregs 20220725.1
Failed test:
Error message:
The text was updated successfully, but these errors were encountered: