• Home
  • Features
  • Pricing
  • Docs
  • Announcements
  • Sign In

FlexMeasures / flexmeasures / 30830067598
84%
main: 84%

Build:
Build:
LAST BUILD BRANCH: feat/internal-commodity-balance
DEFAULT BRANCH: main
Ran 03 Aug 2026 04:08PM UTC
Jobs 1
Files 175
Run time 1min
Badge
Embed ▾
README BADGES
x

If you need to use a raster PNG badge, change the '.svg' to '.png' in the link

Markdown

Textile

RDoc

HTML

Rst

03 Aug 2026 03:59PM UTC coverage: 83.737% (+0.08%) from 83.653%
30830067598

Pull #2385

github

Flix6x
Run the scheduler constraint tests under both backends

Since #2364 the schedulers build the same model twice, once through Pyomo and
once directly in HiGHS, so a test of scheduler behaviour only means something
under one backend if the two agree -- which is the thing that cannot be assumed.
Only test_solver.py was parametrized, so most constraint behaviour was verified
under the configured default and no other. That is how a fix could pass on the
Pyomo path and fail on the direct one, as happened on #2355.

A module now opts in with RUN_UNDER_EACH_SOLVER = True and an autouse fixture in
conftest does the switching, so no test signature changes. Enabled on
test_group_constraints.py and test_operation_modes.py (27 tests, now 54).

test_commitments.py and test_storage.py are NOT enabled, and the reason is worth
recording: they build assets with fixed names, so running each test twice in one
fixture scope violates generic_asset's unique-name constraint. Parametrizing
them means making those fixtures unique per parameter first, which is a larger
change than this one.

Rather than leave that hole silent, test_solver_coverage.py asserts every
planning test module either opts in or appears on an EXEMPT list with a reason,
and that no EXEMPT entry is stale. A new module is then a decision someone makes
on purpose instead of a gap nobody notices.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01X2jLjsQzwztDc7Nxz1ozmQ
Signed-off-by: F.N. Claessen <claessen@seita.nl>
Pull Request #2385: Run the scheduler constraint tests under both backends

17012 of 20316 relevant lines covered (83.74%)

0.84 hits per line

Jobs
ID Job ID Ran Files Coverage
1 30830067598.1 03 Aug 2026 04:08PM UTC 175
83.74
GitHub Action Run
Source Files on build 30830067598
  • Tree
  • List 175
  • Changed 1
  • Source Changed 0
  • Coverage Changed 1
Coverage ∆ File Lines Relevant Covered Missed Hits/Line
  • Back to Repo
  • Github Actions Build #30830067598
  • Pull Request #2385
  • PR Base - main (#30826076910)
STATUS · Troubleshooting · Open an Issue · Sales · Support · CAREERS · ENTERPRISE · START FREE TRIAL · SCHEDULE DEMO
ANNOUNCEMENTS · TWITTER · TOS & SLA · Supported CI Services · What's a CI service? · Automated Testing

© 2026 Coveralls, Inc