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.

Sign up for GitHub

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

Jump to bottom

JIT: Keep delegate object alive during invoke #105099

Closed
wants to merge 21 commits into from

Update lower.cpp

126fca9
Select commit
Loading
Failed to load commit list.
Closed

JIT: Keep delegate object alive during invoke #105099

Update lower.cpp
126fca9
Select commit
Loading
Failed to load commit list.
Azure Pipelines / runtime-coreclr jitstress-isas-sve failed Aug 2, 2024 in 47m 28s

Build #20240801.20 failed

13 errors / 0 warnings

Annotations

Check failure on line 0 in MSBUILD

See this annotation in the file changed.

@azure-pipelines azure-pipelines / runtime-coreclr jitstress-isas-sve

MSBUILD#L0 

MSBUILD(0,0): error MSB4166: Child node "2" exited prematurely. Shutting down. Diagnostic information may be found in files in "/__w/1/s/artifacts/log/MsbuildDebugLogs" and will be named MSBuild_*.failure.txt. This location can be changed by setting the MSBUILDDEBUGPATH environment variable to a different directory.

Check failure on line 0 in MSBUILD

See this annotation in the file changed.

@azure-pipelines azure-pipelines / runtime-coreclr jitstress-isas-sve

MSBUILD#L0 

MSBUILD(0,0): error MSB4166: /__w/1/s/artifacts/log/MsbuildDebugLogs/MSBuild_pid-39905_3321b4c0dd784609a38344d72b8628b5.failure.txt:

Check failure on line 0 in MSBUILD

See this annotation in the file changed.

@azure-pipelines azure-pipelines / runtime-coreclr jitstress-isas-sve

MSBUILD#L0 

MSBUILD(0,0): error MSB4166: UNHANDLED EXCEPTIONS FROM PROCESS 39905:

Check failure on line 0 in MSBUILD

See this annotation in the file changed.

@azure-pipelines azure-pipelines / runtime-coreclr jitstress-isas-sve

MSBUILD#L0 

MSBUILD(0,0): error MSB4166: =====================
View more details on Azure Pipelines