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
MonoAotLLVM runtime is not actually AOTing things #1887
Comments
Example of the log showing the exit 1 message (this is using the benchmarks in dotnet/performance):
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
If you try to do a run with --runtimes monoaotllvm, the run will suceed, but it is not actually aoting anything. A careful examination of the output shows the build of the generated project
exited with 1
. It does however build enough to continue execution, but skips the AOT step. Trying to manually build the generated project shows the underlying error:/Users/naricc/workspace/performance-clean/artifacts/bin/MicroBenchmarks/Release/net7.0/Job-QULCUH/BenchmarkDotNet.Autogenerated.csproj(52,4): error MSB4044: The "MonoAOTCompiler" task was not given a value for the required parameter "IntermediateOutputPath"
This is because
IntermediateOuputPath
was added as a required parameter to the MonoAotCompilerTask by this change:dotnet/runtime#59153
Example command:
This is a pretty easy fix. But is there a way to get this to fail fast if similar issues come up in the future? This went undetected for a long time because it does not fail the run. @adamsitnik
The text was updated successfully, but these errors were encountered: