Skip to content

Restores Benchmarks - #337

Merged
BradyPlanden merged 4 commits into
developfrom
333-bug-update-benchmarks-post-255
May 31, 2024
Merged

Restores Benchmarks#337
BradyPlanden merged 4 commits into
developfrom
333-bug-update-benchmarks-post-255

Conversation

@BradyPlanden

@BradyPlanden BradyPlanden commented May 31, 2024

Copy link
Copy Markdown
Member

Description

This PR does the following:

  • Restore benchmarks to working order,
  • Modify CI triggers to be twice a week for benchmarks and once a day for scheduled,
  • Updates incorrect optimiser kwargs catch in base_optimiser to be a UserWarning instead of ValueError. This enables the optimisers to continue and produces a result with the default values.

Issue reference

Fixes #333

Review

Before you mark your PR as ready for review, please ensure that you've considered the following:

  • Updated the CHANGELOG.md in reverse chronological order (newest at the top) with a concise description of the changes, including the PR number.
  • Noted any breaking changes, including details on how it might impact existing functionality.

Type of change

  • New Feature: A non-breaking change that adds new functionality.
  • Optimization: A code change that improves performance.
  • Examples: A change to existing or additional examples.
  • Bug Fix: A non-breaking change that addresses an issue.
  • Documentation: Updates to documentation or new documentation for new features.
  • Refactoring: Non-functional changes that improve the codebase.
  • Style: Non-functional changes related to code style (formatting, naming, etc).
  • Testing: Additional tests to improve coverage or confirm functionality.
  • Other: (Insert description of change)

Key checklist:

  • No style issues: $ pre-commit run (or $ nox -s pre-commit) (see CONTRIBUTING.md for how to set this up to run automatically when committing locally, in just two lines of code)
  • All unit tests pass: $ nox -s tests
  • The documentation builds: $ nox -s doctest

You can run integration tests, unit tests, and doctests together at once, using $ nox -s quick.

Further checks:

  • Code is well-commented, especially in complex or unclear areas.
  • Added tests that prove my fix is effective or that my feature works.
  • Checked that coverage remains or improves, and added tests if necessary to maintain or increase coverage.

Thank you for contributing to our project! Your efforts help us to deliver great software.

…e a week for benchmarks, once a day for scheduled, updt. incorrect optimiser kwargs to be a warning
@BradyPlanden BradyPlanden linked an issue May 31, 2024 that may be closed by this pull request
@codecov

codecov Bot commented May 31, 2024

Copy link
Copy Markdown

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 97.07%. Comparing base (501064d) to head (0d58d08).
Report is 568 commits behind head on develop.

Additional details and impacted files
@@             Coverage Diff             @@
##           develop     #337      +/-   ##
===========================================
- Coverage    97.18%   97.07%   -0.11%     
===========================================
  Files           41       41              
  Lines         2273     2224      -49     
===========================================
- Hits          2209     2159      -50     
- Misses          64       65       +1     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

@NicolaCourtier NicolaCourtier left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Thanks for the updates @BradyPlanden!

@BradyPlanden
BradyPlanden merged commit 4de2c2e into develop May 31, 2024
@BradyPlanden
BradyPlanden deleted the 333-bug-update-benchmarks-post-255 branch May 31, 2024 14:18
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.

[Bug]: Update benchmarks post #255

2 participants