-
Notifications
You must be signed in to change notification settings - Fork 519
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
Link FrameworkList.xml to a place where MSBuild SDK actually expects it #10928
Conversation
/azp run |
Azure Pipelines successfully started running 1 pipeline(s). |
🔥 Tests failed catastrophically on Build (no summary found). 🔥Result file $(TEST_SUMMARY_PATH) not found. Pipeline on Agent |
This is the failure:
My guess is that the target directory doesn't exist. You can probably repro this locally by doing this from the root directory (this will do a clean build):
|
Thanks. I am doing the local build on clean machine now. I likely didn't notice it because I was testing the steps manually before and I created the directories and links by hand earlier. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
👍
/azp run |
Azure Pipelines successfully started running 1 pipeline(s). |
I don't think we've had a PR that fixes that many issues before.. |
I'd like to at least manually verify the packages once they are built. I also have a build test written locally but I need to fix my Xcode installation first so I can run it. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🎉
@filipnavara I'll make sure that pkgs are created and will post links here. |
@filipnavara FYI: ba7c837 |
@mandel-macaque Thanks a lot. I'm still playing with some trivial test to ensure that everything is working properly: |
@filipnavara do you need that last commit too? |
@mandel-macaque Nah, just the first two. |
Unfortunately the packaging fails [which I anticipated] by having the symlinks point to wrong location:
I suppose I need to modify it to make the symlink with absolute path. Is there any way to make the packages locally? Or can you give me pointer on how the other symlinks are handled? I also have an alternative solution without symlinks but I would like to understand the process nevertheless. |
This is handled by using Example:
Unfortunately the code to build the package is not public. |
@rolfbjarne Thanks. Makes a lot more sense. Ready for take two on the package build :-) |
New build has been scheduled! |
Failure:
This is in a private part of our build, so I'll have a look. |
It's the symlinks pointing to non-existing file. Just fails at that particular point because it's the first task accessing the file through the symlink. Sorry for the slow turn around, it's quite tricky for me to test these changes locally. |
I manually verified the latest package on my test case so dropping the draft status. |
We should backport this to xcode12.5 and d16-9 once it is merged |
There's still some Mac Catalyst test failing. I'll try to see if I can reproduce it locally with the packages. If there's any more detailed error message it would be helpful. |
@filipnavara I think your changes are ok and unrelated to the failure on device tests, the PR tests seems to be fine #10928 (comment) I'll let @rolfbjarne confirm and the merge decision. |
The only test result we care about at the moment is this one: #10928 (comment), and that's green. |
/sudo backport d16-9 |
/sudo backport xcdoe12.5 |
Backport Job to branch d16-9 Created! The magic is happening here |
Backport Job to branch xcdoe12.5 Created! The magic is happening here |
Hooray! Backport succeeded! Please see https://devdiv.visualstudio.com/DevDiv/_build/results?buildId=4587204 for more details. |
/sudo backport xcode12.5 |
Backport Job to branch xcode12.5 Created! The magic is happening here |
Hooray! Backport succeeded! Please see https://devdiv.visualstudio.com/DevDiv/_build/results?buildId=4587227 for more details. |
The SDK conflict resolution code expects the FrameworkList.xml file to be located in
$(TargetFrameworkDirectory)/RedistList/FrameworkList.xml
.Should fix
dotnet/runtime#49211
dotnet/runtime#49940
dotnet/runtime#49477
#10912
#10839
#10548
#10592
mono/mono#20805
mono/mono#20894