fix: increase build timeout seconds to fix flaky CI tests

Author: filzrev

tests/BenchmarkDotNet.IntegrationTests/CustomBuildConfigurationTests.cs

@@ -1,6 +1,7 @@
 using System;
 using System.Reflection;
 using BenchmarkDotNet.Attributes;
+using BenchmarkDotNet.Configs;
 using BenchmarkDotNet.Extensions;
 using BenchmarkDotNet.Jobs;
 using BenchmarkDotNet.Portability;
@@ -24,6 +25,7 @@ public void UserCanSpecifyCustomBuildConfiguration()
             var jobWithCustomConfiguration = Job.Dry.WithCustomBuildConfiguration("CUSTOM");
 
             var config = CreateSimpleConfig(job: jobWithCustomConfiguration);
+            config = ((ManualConfig)config).WithBuildTimeout(TimeSpan.FromSeconds(240));
 
             var report = CanExecute<CustomBuildConfiguration>(config);
 

tests/BenchmarkDotNet.IntegrationTests/WasmTests.cs

@@ -37,6 +37,7 @@ public void WasmIsSupported()
                     .WithArguments([new MsBuildArgument($"/p:WasmMainJSPath={mainJsPath}")])
                     .WithRuntime(new WasmRuntime(dotnetVersion, moniker: RuntimeMoniker.WasmNet80, javaScriptEngineArguments: "--expose_wasm --module"))
                     .WithToolchain(WasmToolchain.From(netCoreAppSettings)))
+                .WithBuildTimeout(TimeSpan.FromSeconds(240))
                 .WithOption(ConfigOptions.GenerateMSBuildBinLog, true);
 
             CanExecute<WasmBenchmark>(config);