-
Notifications
You must be signed in to change notification settings - Fork 1k
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
[WIP] Performance tests for Akka, Remote, Cluster in .NET Core #2768
Conversation
@@ -61,7 +61,8 @@ Target "Build" (fun _ -> | |||
(fun p -> | |||
{ p with | |||
Project = project | |||
Configuration = configuration }) | |||
Configuration = configuration | |||
AdditionalArgs = ["--no-incremental"]}) // i.e. "Rebuild" |
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.
Additional change - we should be calling "Rebuild" to be consistent with previous build script.
If this PR is merged, we can take out the BuildRelease step from "Windows Performance Tests" in CI since this only selectively builds the necessary projects to run PerfTests |
|
||
// .NET Core --------------------------------------- | ||
// Publish netcoreapp1.1 performance test assemblies | ||
let performanceTestProjects = !! "./**/*.Tests.Performance.csproj" |
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.
Each test run for performance tests takes 45 minutes right now, we can't just double it. We have to run them separately
Enables performance tests for .NET Core versions of Akka.Tests.Performance, Akka.Remote.Tests.Performance, and Akka.Tests.Cluster.Performance. Limits the installation of NBench.Runner.exe to only runs of target:
NBench
since NBench.Runner v1.0.4 includes .NET Core standalone executables which include the .NET Core 1.1 runtime.