Conversation
|
/azp run dotnet-unified-build-full |
|
Azure Pipelines successfully started running 1 pipeline(s). |
@jkoritzinsky, this one seems like related to RID graph. |
|
I think this is just dotnet/sdk#50674 and the fix hasn't made it into VMR main yet |
|
The timeouts are #2513 and the WiX issues in Windows_x64_BuildPass2 are probably related to the recent WiX v5 bump ( |
Looks like https://github.com/dotnet/sdk/pull/50682/files was applied in d7e0124. Since it is failing on Line 33 in 5c817e9 |
|
@am11 I think you might need to add |
|
Looks like that too didn't work. :( |
|
@jkoritzinsky, when you get a chance, please take a look. Feel free to push to the branch. We can then apply the changes to dotnet/runtime#117436 and close this one; once the CI is green. 🙂 |
|
Wow, merging main fixed it! Probably some other change in main might have helped. 😁
Can we try this one again? @steveisok, do you remember which official pipeline failed when part of cDAC configs were reverted in #1464 (and does |
If I remember correctly, it's our internal |
|
the public one should be equivalent I think, let's try |
|
/azp run dotnet-unified-build-full |
|
Azure Pipelines successfully started running 1 pipeline(s). |
I kicked off an internal one yesterday and it looked good. Glad you commented because I would have forgot to follow up ;-) |
|
Thank you for testing! I have pushed the additional commit to upstream PR: dotnet/runtime#117436. We can close this and merge that one once CI/BA is green. |
|
All linux legs have passed. osx-arm64 leg is stuck around emsdk build. Closing. Thanks everyone for support! :) |
Testing CI for dotnet/runtime#117436.
@jkoritzinsky @akoeplinger could you please re-run the legs that were failing earlier (dotnet/runtime#117436 (comment))? That would help confirm whether the issue is resolved before the runtime PR gets merged.