Skip to content
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

Patch Tuesday for November 2024 #42165

Merged
merged 32 commits into from
Nov 19, 2024

Conversation

BillyONeal
Copy link
Member

@BillyONeal BillyONeal commented Nov 14, 2024

  • Move Azure Region WestUS3 -> WestUS
  • Update Visual Studio to 17.11.6.
  • Update the Windows SDK to the current version. This required working around https://developercommunity.visualstudio.com/t/NAN-is-no-longer-compile-time-constant-i/10688907 in a few ports
  • Update PowerShell to 7.4.6.
  • Update Azure-CLI to 2.66.0.
  • Remove the WDK as this appears to be unused.
  • Synchronize the Linux image minting JSON with as-deployed.
  • Upgrade from PublishBuildArtifacts@1 to PublishPipelineArtifact@1
  • Add arm64-windows-static-md as requested by Azure Core.
  • Fixed [chartdir]'s supports expression to match its portfile.cmake.
  • Fixed [freeopcua] needing /bigobj and combined patches of patches.
  • Enabled ports skipped for not having 'stable download URLs' now that we have asset caching.

@BillyONeal BillyONeal closed this Nov 14, 2024
@BillyONeal
Copy link
Member Author

I forgot to make the Azure DevOps changes. Will deploy that and reopen.

@BillyONeal BillyONeal reopened this Nov 15, 2024
@BillyONeal
Copy link
Member Author

/azp run

Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@MonicaLiu0311 MonicaLiu0311 added info:internal This PR or Issue was filed by the vcpkg team. category:infrastructure Pertaining to the CI/Testing infrastrucutre labels Nov 15, 2024
JavierMatosD
JavierMatosD previously approved these changes Nov 15, 2024
@BillyONeal
Copy link
Member Author

/azp run

Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@BillyONeal
Copy link
Member Author

##[error]Artifact cannot be uploaded because max quantity has been exceeded or the payment instrument is invalid. https://aka.ms/artbilling for details.

I asked on an internal mailing list if this is expected.

I fixed this by 'setting up billing' but given that pipeline artifacts are documented to be unbillable it seems like a bug in either the product or the docs, I reported.

@BillyONeal BillyONeal closed this Nov 19, 2024
@BillyONeal BillyONeal reopened this Nov 19, 2024
@BillyONeal
Copy link
Member Author

Closed and reopened to kick CLABot

, Callback(callback)
, io(service.GetIOService())
- , Timer(io, boost::posix_time::milliseconds(data.RevisedPublishingInterval))
+ , Timer(io, boost::posix_time::milliseconds((int)data.RevisedPublishingInterval))
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This part used to be in ports/freeopcua/improve_compatibility_with_recent_boost.patch

typedef std::promise<void> Promise;
Promise promise;
+#if BOOST_VERSION >= 107000
+ boost::asio::post(Socket.get_executor(), bind(&Promise::set_value, &promise));
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This part used to be in boost-1.70.patch

@@ -51,14 +99,8 @@ index d42aa65..dd193a9 100644
#include <boost/thread/shared_mutex.hpp>
#include <chrono>
#include <iostream>
@@ -115,5 +115,3 @@ private:

}
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Several of these patches were removing trailing whitespace from the file, I minimized the patch by dropping that edit.

@BillyONeal
Copy link
Member Author

/azp run

Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@@ -68,11 +68,12 @@ index de03564..df3fcf6 100644
- #set(CMAKE_SHARED_LINKER_FLAGS "--no-undefined" )
+ add_definitions(-D_SCL_SECURE_NO_WARNINGS)
+ add_definitions(-D_CRT_SECURE_NO_WARNINGS)
+ add_compile_options(/bigobj)
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The main reason I touched this port was to add this /bigobj because that's what the comment in ci.baseline.txt said it needed, and that appears to be correct :)

@BillyONeal BillyONeal enabled auto-merge (squash) November 19, 2024 20:53
@BillyONeal BillyONeal merged commit 0857a4b into microsoft:master Nov 19, 2024
17 checks passed
@BillyONeal BillyONeal deleted the patch-tuesday-2024-11 branch November 19, 2024 23:43
@MonicaLiu0311 MonicaLiu0311 added the info:reviewed Pull Request changes follow basic guidelines label Nov 20, 2024
@Neumann-A
Copy link
Contributor

@BillyONeal: Any tips to make easyhook work? I simply cannot get it to pass the post build checks. What exactly needs to be installed by VS?

@BillyONeal
Copy link
Member Author

@BillyONeal: Any tips to make easyhook work? I simply cannot get it to pass the post build checks. What exactly needs to be installed by VS?

It's currently working in CI. When it failed before it complained about .NET targeting stuff not being installed.

@Neumann-A
Copy link
Contributor

It's currently working in CI. When it failed before it complained about .NET targeting stuff not being installed.

Did it really complain about that or did it fail because the EasyHook.dll does not export any symbols?

@BillyONeal
Copy link
Member Author

Did it really complain about that or did it fail because the EasyHook.dll does not export any symbols?

It failed because easyhook explicitly asks for .NET things in its build system.

@BillyONeal
Copy link
Member Author

MSBuild version 17.11.9+a69bbaaf5 for .NET Framework
Build started 11/15/2024 3:36:06 PM.

     1>Project "D:\b\easyhook\x64-windows-rel\EasyHook.sln" on node 1 (EasyHookDll target(s)).
     1>ValidateSolutionConfiguration:
         Building solution configuration "netfx4-Release|x64".
       ValidateProjects:
         The project "EasyHook.Tests" is not selected for building in solution configuration "netfx4-Release|x64".
     1>Project "D:\b\easyhook\x64-windows-rel\EasyHook.sln" (1) is building "D:\b\easyhook\x64-windows-rel\EasyHookDll\EasyHookDll.vcxproj" (2) on node 1 (default targets).
     2>Project "D:\b\easyhook\x64-windows-rel\EasyHookDll\EasyHookDll.vcxproj" (2) is building "D:\b\easyhook\x64-windows-rel\EasyHookSvc\EasyHookSvc.csproj" (3:2) on node 1 (default targets).
     3>C:\Program Files\Microsoft Visual Studio\2022\Enterprise\MSBuild\Current\Bin\amd64\Microsoft.Common.CurrentVersion.targets(1259,5): error MSB3644: The reference assemblies for .NETFramework,Version=v4.7.2 were not found. To resolve this, install the Developer Pack (SDK/Targeting Pack) for this framework version or retarget your application. You can download .NET Framework Developer Packs at https://aka.ms/msbuild/developerpacks [D:\b\easyhook\x64-windows-rel\EasyHookSvc\EasyHookSvc.csproj]
     3>_CleanRecordFileWrites:
         Creating directory "obj\netfx4-Release\".
     3>Done Building Project "D:\b\easyhook\x64-windows-rel\EasyHookSvc\EasyHookSvc.csproj" (default targets) -- FAILED.
     2>Project "D:\b\easyhook\x64-windows-rel\EasyHookDll\EasyHookDll.vcxproj" (2) is building "D:\b\easyhook\x64-windows-rel\EasyHook\EasyHook.csproj" (4:2) on node 2 (default targets).
     4>C:\Program Files\Microsoft Visual Studio\2022\Enterprise\MSBuild\Current\Bin\amd64\Microsoft.Common.CurrentVersion.targets(1259,5): error MSB3644: The reference assemblies for .NETFramework,Version=v4.7.2 were not found. To resolve this, install the Developer Pack (SDK/Targeting Pack) for this framework version or retarget your application. You can download .NET Framework Developer Packs at https://aka.ms/msbuild/developerpacks [D:\b\easyhook\x64-windows-rel\EasyHook\EasyHook.csproj]
     4>_CleanRecordFileWrites:
         Creating directory "obj\netfx4-Release\".
     4>Done Building Project "D:\b\easyhook\x64-windows-rel\EasyHook\EasyHook.csproj" (default targets) -- FAILED.
     2>Done Building Project "D:\b\easyhook\x64-windows-rel\EasyHookDll\EasyHookDll.vcxproj" (default targets) -- FAILED.
     1>Done Building Project "D:\b\easyhook\x64-windows-rel\EasyHook.sln" (EasyHookDll target(s)) -- FAILED.

Build FAILED.

       "D:\b\easyhook\x64-windows-rel\EasyHook.sln" (EasyHookDll target) (1) ->
       "D:\b\easyhook\x64-windows-rel\EasyHookDll\EasyHookDll.vcxproj" (default target) (2) ->
       "D:\b\easyhook\x64-windows-rel\EasyHookSvc\EasyHookSvc.csproj" (default target) (3:2) ->
       (GetReferenceAssemblyPaths target) -> 
         C:\Program Files\Microsoft Visual Studio\2022\Enterprise\MSBuild\Current\Bin\amd64\Microsoft.Common.CurrentVersion.targets(1259,5): error MSB3644: The reference assemblies for .NETFramework,Version=v4.7.2 were not found. To resolve this, install the Developer Pack (SDK/Targeting Pack) for this framework version or retarget your application. You can download .NET Framework Developer Packs at https://aka.ms/msbuild/developerpacks [D:\b\easyhook\x64-windows-rel\EasyHookSvc\EasyHookSvc.csproj]


       "D:\b\easyhook\x64-windows-rel\EasyHook.sln" (EasyHookDll target) (1) ->
       "D:\b\easyhook\x64-windows-rel\EasyHookDll\EasyHookDll.vcxproj" (default target) (2) ->
       "D:\b\easyhook\x64-windows-rel\EasyHook\EasyHook.csproj" (default target) (4:2) ->
         C:\Program Files\Microsoft Visual Studio\2022\Enterprise\MSBuild\Current\Bin\amd64\Microsoft.Common.CurrentVersion.targets(1259,5): error MSB3644: The reference assemblies for .NETFramework,Version=v4.7.2 were not found. To resolve this, install the Developer Pack (SDK/Targeting Pack) for this framework version or retarget your application. You can download .NET Framework Developer Packs at https://aka.ms/msbuild/developerpacks [D:\b\easyhook\x64-windows-rel\EasyHook\EasyHook.csproj]

    0 Warning(s)
    2 Error(s)

Time Elapsed 00:00:00.71

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
category:infrastructure Pertaining to the CI/Testing infrastrucutre info:internal This PR or Issue was filed by the vcpkg team. info:reviewed Pull Request changes follow basic guidelines
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants