Skip to content

CI for performance tests #992

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

Merged
merged 25 commits into from
Feb 13, 2020
Merged

Conversation

lostmsu
Copy link
Member

@lostmsu lostmsu commented Nov 21, 2019

What does this implement/fix? Explain your changes.

Runs performance tests in CI, comparing build with new changes against the latest (2.3 as of now) NuGet release.

Does this close any currently open issues?

#886

Checklist

Nothing applicable.

@lostmsu lostmsu added the WIP label Nov 21, 2019
@lostmsu lostmsu force-pushed the features/PerfTests-CI branch from b357460 to d15d25d Compare November 21, 2019 05:10
@codecov-io
Copy link

codecov-io commented Nov 21, 2019

Codecov Report

Merging #992 into master will not change coverage.
The diff coverage is n/a.

Impacted file tree graph

@@           Coverage Diff           @@
##           master     #992   +/-   ##
=======================================
  Coverage   86.75%   86.75%           
=======================================
  Files           1        1           
  Lines         302      302           
=======================================
  Hits          262      262           
  Misses         40       40
Flag Coverage Δ
#setup_linux 65.56% <ø> (ø) ⬆️
#setup_windows 71.52% <ø> (ø) ⬆️

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update a6c55d4...031e8bb. Read the comment docs.

@lostmsu lostmsu removed the WIP label Nov 21, 2019
@lostmsu lostmsu requested a review from filmor November 21, 2019 17:36
@lostmsu
Copy link
Member Author

lostmsu commented Nov 21, 2019

@filmor if you are to merge this, I recommend squashing the commit, as there are many intermediate changes, which are insignificant on their own.

@lostmsu lostmsu removed the request for review from filmor November 21, 2019 17:39
@lostmsu lostmsu added the WIP label Nov 21, 2019
@lostmsu lostmsu force-pushed the features/PerfTests-CI branch from af473de to 0eec424 Compare November 21, 2019 20:00
@lostmsu lostmsu removed the WIP label Nov 21, 2019
@lostmsu
Copy link
Member Author

lostmsu commented Nov 21, 2019

OK, test is passing, and I can see in AppVeyor logs for 3.5 x64 xplat build, that performance is checked.

BTW, 3.5 x64 xplat is the only configuration where perf test runs, as it is the only configuration supported by the published NuGet package.

@lostmsu lostmsu requested a review from filmor November 21, 2019 22:01
@lostmsu lostmsu changed the title WIP: CI for performance tests CI for performance tests Nov 22, 2019
@lostmsu
Copy link
Member Author

lostmsu commented Nov 23, 2019

I guess this boils down to how much flakiness we can tolerate in perf tests in CI. Letting a bit more wiggle room in the performance goal should make it very unlikely to fail randomly.

@lostmsu lostmsu force-pushed the features/PerfTests-CI branch from 430ea6e to a6c55d4 Compare January 31, 2020 20:33
@filmor filmor merged commit f5548e3 into pythonnet:master Feb 13, 2020
AlexCatarino pushed a commit to QuantConnect/pythonnet that referenced this pull request Jun 27, 2020
* attempted to add performance tests to CI
* attempt to fix PerformanceTests xplat CI build
* enabling building PerformanceTests for Mono
* fixed AppVeyor path to Python.PerformanceTests.dll
* fixed Mono deb sources to bionic
* slightly relaxed perf target for WriteInt64Property
* PerformanceTests: explicitly specify platform
* use framework-specific build of perf tests in xplat and generic otherwise
* added perf tests run to Travis CI
* better error message for a failure to run benchmarks
* appveyor: don't run perf tests in unsupported configurations
* fixed performance test Python version condition in AppVeyor
* explicitly notify when performance tests are skipped in AppVeyor
* relax performance targets to ~10%, improve perf failure message
* switch to the release of Microsoft.NETFramework.ReferenceAssemblies package
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants