I have just opened the issue
#74842
tracking recent failures in Crossgen2 comparison runs in the runtime-coreclr crossgen2 outerloop runs. It turns out that today lab artifacts are insufficient to root cause the bug. In case of failure, we should copy the Crossgen2 compilation artifacts to the machine dump folder so that they get copied to Azure and can be later downloaded and analyzed for root causing the problem.
/cc @dotnet/crossgen-contrib, @davidwrighton
I have just opened the issue
#74842
tracking recent failures in Crossgen2 comparison runs in the runtime-coreclr crossgen2 outerloop runs. It turns out that today lab artifacts are insufficient to root cause the bug. In case of failure, we should copy the Crossgen2 compilation artifacts to the machine dump folder so that they get copied to Azure and can be later downloaded and analyzed for root causing the problem.
/cc @dotnet/crossgen-contrib, @davidwrighton