You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Feb 23, 2026. It is now read-only.
Repository navigation
This repository was archived by the owner on Feb 23, 2026. It is now read-only.
@davidwrighton it's a random build error that I don't understand why it happens sometimes:
EXEC : error : Unable to load shared library 'jitinterface_x64' or one of its dependencies. In order to help diagnose loading problems, consider using a tool like strace. If you're using glibc, consider setting the LD_DEBUG environment variable: [/home/egorbot/runtime/src/coreclr/crossgen-corelib.proj]
/home/egorbot/runtime/artifacts/bin/coreclr/linux.x64.Release/x64/crossgen2/jitinterface_x64.so: cannot open shared object file: No such file or directory
/home/egorbot/runtime/artifacts/bin/coreclr/linux.x64.Release/x64/crossgen2/libjitinterface_x64.so: cannot open shared object file: No such file or directory
/home/egorbot/runtime/artifacts/bin/coreclr/linux.x64.Release/x64/crossgen2/jitinterface_x64: cannot open shared object file: No such file or directory
/home/egorbot/runtime/artifacts/bin/coreclr/linux.x64.Release/x64/crossgen2/libjitinterface_x64: cannot open shared object file: No such file or directory
let me debug it again.. must be some LIBC mismatch
Yup, but I was asking if David wants to compare the previous PR because this one is just a follow up and previous PR had few commits before the merge which weren't benchmarked.
Activity
EgorBot commentedon Mar 24, 2025
❌ Failed on AzureGenoa: Job failed, see logs.
cc @davidwrighton (logs). EgorBot manual: link.
EgorBot commentedon Mar 24, 2025
❌ Failed on AzureCobalt100: Job failed, see logs.
cc @davidwrighton (logs). EgorBot manual: link.
EgorBo commentedon Mar 24, 2025
@davidwrighton it's a random build error that I don't understand why it happens sometimes:
let me debug it again.. must be some LIBC mismatch
EgorBo commentedon Mar 24, 2025
Windows job should finish just fine
EgorBo commentedon Mar 24, 2025
it's dotnet/runtime#111731
EgorBot commentedon Mar 24, 2025
Benchmark results on
windows_azure_cascadelakeBDN_Artifacts.zip
cc @davidwrighton (agent_logs.txt). EgorBot manual: link.
EgorBo commentedon Mar 24, 2025
Ok, seems that I've fixed the problem with a workaround
EgorBo commentedon Mar 24, 2025
@EgorBot -amd -arm -pr 113857
davidwrighton commentedon Mar 24, 2025
@EgorBo thank you. I was really hoping not to burden you with more work.
EgorBot commentedon Mar 24, 2025
Benchmark results on
linux_azure_cobalt100BDN_Artifacts.zip
cc @EgorBo (agent_logs.txt). EgorBot manual: link.
EgorBot commentedon Mar 24, 2025
Benchmark results on
linux_azure_genoaBDN_Artifacts.zip
cc @EgorBo (agent_logs.txt). EgorBot manual: link.
EgorBo commentedon Mar 24, 2025
No problem! I wanted to fix this issue for quite some time
am11 commentedon Mar 24, 2025
Do we want to run comparisons with https://github.com/dotnet/runtime/commits/ac13edc2df258639b106edfe88147520d0ff3247, one commit in main before dotnet/runtime#113242 was merged?
or only dotnet/runtime#113857 vs. main?
EgorBo commentedon Mar 25, 2025
The bot compares PR vs current tip of Main
am11 commentedon Mar 25, 2025
Yup, but I was asking if David wants to compare the previous PR because this one is just a follow up and previous PR had few commits before the merge which weren't benchmarked.