-
Notifications
You must be signed in to change notification settings - Fork 516
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
[dotnet][xma] Ensure we don't use DOTNET_ROOT and DOTNET_HOST_PATH in… #18567
Conversation
|
|
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
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.
Looks like this is breaking the macOS tests
Creating directory "obj/Debug/net7.0-macos/macOS/".
/Users/builder/azdo/_work/_tool/dotnet/dotnet /Users/builder/azdo/_work/3/s/xamarin-macios/builds/downloads/dotnet-sdk-7.0.206-servicing.23254.11/packs/Microsoft.macOS.Sdk/13.3.7351-ci.pr.gh18567/tools/lib/bgen/bgen.dll @/Users/builder/azdo/_work/3/s/xamarin-macios/tests/bindings-test/dotnet/macOS/obj/Debug/net7.0-macos/response-file.rsp
It was not possible to find any compatible framework version
The framework 'Microsoft.NETCore.App', version '7.0.0' was not found.
- The following frameworks were found:
5.0.17 at [/Users/builder/azdo/_work/_tool/dotnet/shared/Microsoft.NETCore.App]
You can resolve the problem by installing the specified framework and/or SDK.
The specified framework can be found at:
- https://aka.ms/dotnet-core-applaunch?framework=Microsoft.NETCore.App&framework_version=7.0.0&arch=x64&rid=osx.11.2-x64
1>/Users/builder/azdo/_work/3/s/xamarin-macios/builds/downloads/dotnet-sdk-7.0.206-servicing.23254.11/packs/Microsoft.macOS.Sdk/13.3.7351-ci.pr.gh18567/tools/msbuild/macOS/Xamarin.Shared.targets(1736,3): error MSB6006: "dotnet" exited with code 150. [/Users/builder/azdo/_work/3/s/xamarin-macios/tests/bindings-test/dotnet/macOS/bindings-test.csproj]
1>Done Building Project "/Users/builder/azdo/_work/3/s/xamarin-macios/tests/bindings-test/dotnet/macOS/bindings-test.csproj" (default targets) -- FAILED.
Deferred Messages
… the Build Agent and remote tasks DOTNET_ROOT and DOTNET_HOST_PATH are being deprecated as a mechanism to store the location of dotnet. PATH will be used instead, so we should ensure that the existing code that makes usage of these variables is adapted to the new guidelines. More information: dotnet/roslyn@f454d69 dotnet/runtime#88754 (comment) Additionally, to avoid confusion, we are using a dedicate DOTNET_CUSTOM_PATH variable with the path of the dotnet used by the XMA Build Agent, so it can be used internally by the tasks without mixing it with the existing dotnet variables
|
💻 [PR Build] Tests on macOS M1 - Mac Ventura (13.0) passed 💻✅ All tests on macOS M1 - Mac Ventura (13.0) passed. Pipeline on Agent |
📚 [PR Build] Artifacts 📚Packages generatedView packagesPipeline on Agent |
💻 [CI Build] Windows Integration Tests passed 💻✅ All Windows Integration Tests passed. Pipeline on Agent |
💻 [PR Build] Tests on macOS M1 - Mac Big Sur (11.5) passed 💻✅ All tests on macOS M1 - Mac Big Sur (11.5) passed. Pipeline on Agent |
✅ API diff for current PR / commitLegacy Xamarin (No breaking changes)
NET (empty diffs)
❗ API diff vs stable (Breaking changes)Legacy Xamarin (:heavy_exclamation_mark: Breaking changes :heavy_exclamation_mark:)
.NET (:heavy_exclamation_mark: Breaking changes :heavy_exclamation_mark:)
✅ Generator diffGenerator diff is empty Pipeline on Agent |
/sudo backport net8.0 |
/sudo backport release/8.0.1xx-preview7 |
Backport Job to branch net8.0 Created! The magic is happening here |
Backport Job to branch release/8.0.1xx-preview7 Created! The magic is happening here |
Hooray! Backport succeeded! Please see https://devdiv.visualstudio.com/DevDiv/_build/results?buildId=8153356 for more details. |
Hooray! Backport succeeded! Please see https://devdiv.visualstudio.com/DevDiv/_build/results?buildId=8153360 for more details. |
🚀 [CI Build] Test results 🚀Test results✅ All tests passed on VSTS: simulator tests. 🎉 All 235 tests passed 🎉 Tests counts✅ bcl: All 69 tests passed. Html Report (VSDrops) Download Pipeline on Agent |
…OOT and DOTNET_HOST_PATH in. (#18591) . the Build Agent and remote tasks DOTNET_ROOT and DOTNET_HOST_PATH are being deprecated as a mechanism to store the location of dotnet. PATH will be used instead, so we should ensure that the existing code that makes usage of these variables is adapted to the new guidelines. More information: dotnet/roslyn@f454d69 dotnet/runtime#88754 (comment) Additionally, to avoid confusion, we are using a dedicate DOTNET_CUSTOM_PATH variable with the path of the dotnet used by the XMA Build Agent, so it can be used internally by the tasks without mixing it with the existing dotnet variables Backport of #18567 --------- Co-authored-by: Mauro Agnoletti <[email protected]> Co-authored-by: GitHub Actions Autoformatter <[email protected]>
…T_PATH in. (#18590) . the Build Agent and remote tasks DOTNET_ROOT and DOTNET_HOST_PATH are being deprecated as a mechanism to store the location of dotnet. PATH will be used instead, so we should ensure that the existing code that makes usage of these variables is adapted to the new guidelines. More information: dotnet/roslyn@f454d69 dotnet/runtime#88754 (comment) Additionally, to avoid confusion, we are using a dedicate DOTNET_CUSTOM_PATH variable with the path of the dotnet used by the XMA Build Agent, so it can be used internally by the tasks without mixing it with the existing dotnet variables Backport of #18567 --------- Co-authored-by: Mauro Agnoletti <[email protected]> Co-authored-by: GitHub Actions Autoformatter <[email protected]>
… the Build Agent and remote tasks
DOTNET_ROOT and DOTNET_HOST_PATH are being deprecated as a mechanism to store the location of dotnet. PATH will be used instead, so we should ensure that the existing code that makes usage of these variables is adapted to the new guidelines. More information:
dotnet/roslyn@f454d69
dotnet/runtime#88754 (comment)
Additionally, to avoid confusion, we are using a dedicate DOTNET_CUSTOM_PATH variable with the path of the dotnet used by the XMA Build Agent, so it can be used internally by the tasks without mixing it with the existing dotnet variables