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

JIT/Performance/CodeQuality/Bytemark/Bytemark failed with Assert failure: al->alloc_list_tail() == 0 #105201

Open
jakobbotsch opened this issue Jul 21, 2024 · 4 comments
Assignees
Labels
area-GC-coreclr blocking-clean-ci Blocking PR or rolling runs of 'runtime' or 'runtime-extra-platforms' Known Build Error Use this to report build issues in the .NET Helix tab
Milestone

Comments

@jakobbotsch
Copy link
Member

jakobbotsch commented Jul 21, 2024

Build Information

Build: https://dev.azure.com/dnceng-public/cbb18261-c48f-4abb-8651-8cdcb5474649/_build/results?buildId=749347
Build error leg or test failing: JIT/Performance/CodeQuality/Bytemark/Bytemark/Bytemark.cmd
Pull request: #105196

Error Message

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

{
  "ErrorMessage": "al->alloc_list_tail() == 0",
  "ErrorPattern": "",
  "BuildRetry": false,
  "ExcludeConsoleLog": false
}

Known issue validation

Build: 🔎 https://dev.azure.com/dnceng-public/public/_build/results?buildId=749347
Error message validated: [al->alloc_list_tail() == 0]
Result validation: ✅ Known issue matched with the provided build.
Validation performed at: 7/21/2024 4:32:13 PM UTC

Report

Build Definition Test Pull Request
788045 dotnet/runtime JIT/Performance/CodeQuality/Bytemark/Bytemark/Bytemark.cmd #106954

Summary

24-Hour Hit Count 7-Day Hit Count 1-Month Count
0 0 1
@jakobbotsch jakobbotsch added blocking-clean-ci Blocking PR or rolling runs of 'runtime' or 'runtime-extra-platforms' Known Build Error Use this to report build issues in the .NET Helix tab labels Jul 21, 2024
@dotnet-issue-labeler dotnet-issue-labeler bot added the needs-area-label An area label is needed to ensure this gets routed to the appropriate area owners label Jul 21, 2024
@dotnet-policy-service dotnet-policy-service bot added the untriaged New issue has not been triaged by the area owner label Jul 21, 2024
@jakobbotsch jakobbotsch added area-GC-coreclr and removed untriaged New issue has not been triaged by the area owner needs-area-label An area label is needed to ensure this gets routed to the appropriate area owners labels Jul 21, 2024
Copy link
Contributor

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

@mangod9 mangod9 added this to the 9.0.0 milestone Aug 1, 2024
@mangod9
Copy link
Member

mangod9 commented Aug 15, 2024

Closing since this hasnt reproed in a few weeks.

@mangod9 mangod9 closed this as completed Aug 15, 2024
@jakobbotsch jakobbotsch reopened this Aug 26, 2024
@jakobbotsch jakobbotsch added Known Build Error Use this to report build issues in the .NET Helix tab and removed Known Build Error Use this to report build issues in the .NET Helix tab labels Aug 26, 2024
@v-wenyuxu
Copy link

Failed in: runtime-coreclr jitstress 20240827.1

Failed tests:

coreclr osx arm64 Checked tailcallstress @ OSX.1200.ARM64.Open
    - JIT/Performance/CodeQuality/Bytemark/Bytemark/Bytemark.cmd

Error message:

 
Assert failure(PID 19124 [0x00004ab4], Thread: 1429884 [0x15d17c]): al->alloc_list_tail() == 0
    File: /Users/runner/work/1/s/src/coreclr/gc/gc.cpp:15956
    Image: /private/tmp/helix/working/B7F90A39/p/corerun

waitpid() returned successfully (wstatus 00000000) WEXITSTATUS 0 WTERMSIG 0
/private/tmp/helix/working/B7F90A39/w/AD6C0972/e/JIT/Performance/JIT.performance/../CodeQuality/Bytemark/Bytemark/Bytemark.sh: line 453: 19124 Abort trap: 6           (core dumped) $LAUNCHER $ExePath "${CLRTestExecutionArguments[@]}"

Return code:      1
Raw output file:      /tmp/helix/working/B7F90A39/w/AD6C0972/uploads/CodeQuality/Bytemark/Bytemark/output.txt
Raw output:
BEGIN EXECUTION
/tmp/helix/working/B7F90A39/p/corerun -p System.Reflection.Metadata.MetadataUpdater.IsSupported=false -p System.Runtime.Serialization.EnableUnsafeBinaryFormatterSerialization=true Bytemark.dll ''
BBBBBB   YYY   Y  TTTTTTT  EEEEEEE
BBB   B  YYY   Y    TTT    EEE
BBB   B  YYY   Y    TTT    EEE
BBBBBB    YYY Y     TTT    EEEEEEE
BBB   B    YYY      TTT    EEE
BBB   B    YYY      TTT    EEE
BBBBBB     YYY      TTT    EEEEEEE

BYTEmark (tm) C# Mode Benchmark ver. 2 (06/99)
NUMERIC SORT(jagged):  Iterations/sec: 2209.94186  Index: 56.67535
NUMERIC SORT(rectangle):  Iterations/sec: 1287.13523  Index: 33.00939
STRING SORT:  Iterations/sec: 27520.34177  Index: 12296.84619
BITFIELD:  Iterations/sec: 476784185.07108  Index: 81.78532
FP EMULATION(struct):  Iterations/sec: 198.24854  Index: 95.12886
FP EMULATION(class):  Iterations/sec: 195.65436  Index: 93.88405
FOURIER:  Iterations/sec: 398137.02624  Index: 452.79994
ASSIGNMENT(jagged):  Iterations/sec: 64.87394  Index: 246.85669
ASSIGNMENT(rectangle):  Iterations/sec: 52.86123  Index: 201.14625
IDEA:  Iterations/sec: 10666.95361  Index: 163.14817
HUFFMAN:  Iterations/sec: 6345.85266  Index: 175.97062
NEURAL NET(jagged):  Iterations/sec: 71.06452  Index: 114.15988
NEURAL NET(rectangle):  Iterations/sec: 55.22170  Index: 88.70956
LU DECOMPOSITION:[createdump] Gathering state for process 19124 
[createdump] Crashing thread 15d17c signal 6 (0006)
[createdump] Writing crash report to file /cores/coredump.19124.dmp.crashreport.json
[createdump] Crash report successfully written
[createdump] Writing minidump with heap to file /cores/coredump.19124.dmp
[createdump] Written 455016616 bytes (27772 pages) to core file
[createdump] Target process is alive
[createdump] Dump successfully written in 1207ms
Expected: 100
Actual: 134
END EXECUTION - FAILED
Test failed. Trying to see if dump file was created in /cores since 8/27/2024 10:35:27 PM
Processing /cores/coredump.19124.dmp.crashreport.json
Printing stacktrace from '/cores/coredump.19124.dmp.crashreport.json'
Invoking llvm-symbolizer --pretty-print
Errors while running llvm-symbolizer --pretty-print
System.ComponentModel.Win32Exception (2): An error occurred trying to start process 'llvm-symbolizer' with working directory '/private/tmp/helix/working/B7F90A39/w/AD6C0972/e/JIT/Performance/JIT.performance'. No such file or directory
   at System.Diagnostics.Process.ForkAndExecProcess(ProcessStartInfo startInfo, String resolvedFilename, String[] argv, String[] envp, String cwd, Boolean setCredentials, UInt32 userId, UInt32 groupId, UInt32[] groups, Int32& stdinFd, Int32& stdoutFd, Int32& stderrFd, Boolean usesTerminal, Boolean throwOnNoExec) in /_/src/libraries/System.Diagnostics.Process/src/System/Diagnostics/Process.Unix.cs:line 496
   at System.Diagnostics.Process.StartCore(ProcessStartInfo startInfo) in /_/src/libraries/System.Diagnostics.Process/src/System/Diagnostics/Process.Unix.cs:line 456
   at System.Diagnostics.Process.Start() in /_/src/libraries/System.Diagnostics.Process/src/System/Diagnostics/Process.cs:line 1284
   at CoreclrTestLib.CoreclrTestWrapperLib.TryPrintStackTraceFromCrashReport(String crashReportJsonFile, TextWriter outputWriter)
Test Harness Exitcode is : 1
To run the test:
Set up CORE_ROOT and run.
> /private/tmp/helix/working/B7F90A39/w/AD6C0972/e/JIT/

Stack trace:

   at Xunit.Assert.True(Nullable`1 condition, String userMessage) in /_/src/Microsoft.DotNet.XUnitAssert/src/BooleanAsserts.cs:line 146
   at Xunit.Assert.True(Boolean condition, String userMessage) in /_/src/Microsoft.DotNet.XUnitAssert/src/BooleanAsserts.cs:line 128
   at TestLibrary.OutOfProcessTest.RunOutOfProcessTest(String assemblyPath, String testPathPrefix)
   at Program.<<Main>$>g__TestExecutor99|0_100(StreamWriter tempLogSw, StreamWriter statsCsvSw, <>c__DisplayClass0_0&)

@mangod9 mangod9 modified the milestones: 9.0.0, 10.0.0 Sep 10, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area-GC-coreclr blocking-clean-ci Blocking PR or rolling runs of 'runtime' or 'runtime-extra-platforms' Known Build Error Use this to report build issues in the .NET Helix tab
Projects
None yet
Development

No branches or pull requests

4 participants