Skip to content
New issue

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

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

Already on GitHub? # to your account

Build failure in RyuJIT for ARM64 #98009

Closed
jkoritzinsky opened this issue Feb 5, 2024 · 1 comment · Fixed by #98011
Closed

Build failure in RyuJIT for ARM64 #98009

jkoritzinsky opened this issue Feb 5, 2024 · 1 comment · Fixed by #98011
Labels
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

Comments

@jkoritzinsky
Copy link
Member

jkoritzinsky commented Feb 5, 2024

Error Blob

 /__w/1/s/src/coreclr/jit/emitarm64.cpp:23309:50: error: too few arguments to function call, expected 2, have 1
              emitDispElementIndex(emitGetInsSC(id));              // iii
              ~~~~~~~~~~~~~~~~~~~~                 ^
  /__w/1/s/src/coreclr/jit/emitarm64.cpp:20910:15: note: 'emitDispElementIndex' declared here
  void emitter::emitDispElementIndex(const ssize_t imm, const bool addComma)
{
  "ErrorMessage": "emitter::emitDispElementIndex",
  "BuildRetry": false,
  "ErrorPattern": "",
  "ExcludeConsoleLog": true
}

cc: @TIHan

Reproduction Steps

No response

Known issue validation

Build: 🔎 https://dev.azure.com/dnceng-public/public/_build/results?buildId=554382
Error message validated: emitter::emitDispElementIndex
Result validation: ✅ Known issue matched with the provided build.
Validation performed at: 2/5/2024 11:50:31 PM UTC

Report

Build Definition Step Name Console log Pull Request
554389 dotnet/runtime Build product Log #98006
554383 dotnet/runtime Build product Log #98008
554380 dotnet/runtime Build product Log #97487
554370 dotnet/runtime Build product Log #97234
554382 dotnet/runtime Build Log #98008
554369 dotnet/runtime Build Log #97234
554363 dotnet/runtime Build product Log
554352 dotnet/runtime Build product Log #98007
554348 dotnet/runtime Build product Log #98007
554351 dotnet/runtime Build Log #98007
554347 dotnet/runtime Build Log #98007
554279 dotnet/runtime Build product Log #97934
554329 dotnet/runtime Build product Log #97972
554324 dotnet/runtime Build product Log
554302 dotnet/runtime Build Log #98006
554299 dotnet/runtime Build Log #98006
554278 dotnet/runtime Build CoreCLR Runtime Log #97934

Summary

24-Hour Hit Count 7-Day Hit Count 1-Month Count
17 17 17
@jkoritzinsky jkoritzinsky 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 Feb 5, 2024
@dotnet-issue-labeler dotnet-issue-labeler bot added the area-CodeGen-coreclr CLR JIT compiler in src/coreclr/src/jit and related components such as SuperPMI label Feb 5, 2024
@build-analysis build-analysis bot removed area-CodeGen-coreclr CLR JIT compiler in src/coreclr/src/jit and related components such as SuperPMI labels Feb 5, 2024
@ghost ghost added the untriaged New issue has not been triaged by the area owner label Feb 5, 2024
@ghost ghost added the in-pr There is an active PR which will close this issue when it is merged label Feb 6, 2024
@TIHan
Copy link
Contributor

TIHan commented Feb 6, 2024

It was a PR race that caused it. I updated my PR before noon today and CI ran successfully, but another PR was merged between then and now before I merged mine.

@ghost ghost removed in-pr There is an active PR which will close this issue when it is merged untriaged New issue has not been triaged by the area owner labels Feb 6, 2024
@github-actions github-actions bot locked and limited conversation to collaborators Mar 7, 2024
# for free to subscribe to this conversation on GitHub. Already have an account? #.
Labels
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

Successfully merging a pull request may close this issue.

2 participants