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

FlexMeasures / flexmeasures / 44190286515
88%

Build:
DEFAULT BRANCH: main
Ran 17 Nov 2026 10:37PM UTC
Jobs 1
Files 196
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

17 Nov 2026 10:27PM UTC coverage: 88.022% (+0.05%) from 87.973%
44190286515

push

github

web-flow
Feat: flexmeasures monitor automations (#2671)

* data/services/automations: record how schedule, report and plugin runs end

Context:
- Only forecast runs followed their jobs, so schedule, report and plugin runs stayed at execution state 'pending' whatever became of their jobs.

Change:
- record_automation_run_jobs records the jobs such a run queued, then takes the outcome of any job that already finished or failed from Redis; a run with no jobs has succeeded.
- The record_outcome_on_automation_run decorator records a job's start, success or failure on its run, found through the job's RQ ID, and wraps make_schedule, the sequential wrap-up job, run_report_job and execute_automation_job.
- Plugin jobs carry automation_run_id in their trigger.
- A schedule that fell back counts as a failed run, as the fallback job is not one of the run's recorded jobs.

Signed-off-by: Mohamed Belhsan Hmida <mohamedbelhsanhmida@gmail.com>

* data/tests: cover how schedule, report and plugin runs end

Context:
- Schedule, report and plugin runs now record how their jobs ended.

Change:
- Schedule runs, single and sequential, succeed once their jobs did and fail with the job's error; a job queued outside a run is not recorded.
- A plugin run records its job's outcome, also when the job finished before the run recorded it.
- Report run tests check the run's outcome: succeeded, nothing to do, and refused.

Signed-off-by: Mohamed Belhsan Hmida <mohamedbelhsanhmida@gmail.com>

* docs: every automation run records how its jobs ended

Context:
- Schedule, report and plugin runs now record how their jobs ended, as forecast runs did.

Change:
- Say which jobs each type of run records, that a run without jobs has succeeded, and that a schedule which fell back counts as failed.

Signed-off-by: Mohamed Belhsan Hmida <mohamedbelhsanhmida@gmail.com>

* changelog: append PR #2670 to the durable automation runs entry

Context:
- Schedule, report and plugin runs now record how their jobs ... (continued)

125 of 127 new or added lines in 5 files covered. (98.43%)

23442 of 26632 relevant lines covered (88.02%)

0.88 hits per line

Uncovered Changes

Lines Coverage ∆ File
1
83.94
4.25% flexmeasures/cli/monitor.py
1
98.33
flexmeasures/data/services/automation_monitoring.py
Jobs
ID Job ID Ran Files Coverage
1 44190286515.1 17 Nov 2026 10:37PM UTC 196
88.02
GitHub Action Run
Source Files on build 44190286515
  • Tree
  • List 196
  • Changed 4
  • Source Changed 4
  • Coverage Changed 4
Coverage ∆ File Lines Relevant Covered Missed Hits/Line
  • Back to Repo
  • Github Actions Build #44190286515
  • 874a2d89 on github
  • Prev Build on main (#43701040441)
  • Next Build on main (#44414398163)
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