FlexMeasures / flexmeasures / 37829207569

87%

Build Type

push

github

Committed by web-flow

Commit Message

One failure summary in a job's meta for every queue (#2698)

* data/services: store one failure summary in a job's meta for every queue

Context:
- #2696: a failed job's meta held the exception object (scheduling), a dict
  (forecasting) or a string (reporting, ingestion and any other queue), and
  its readers formatted the type of whatever was stored. A failed forecasting
  job read "dict: {...}", with its timeout hint lost, and a failed report or
  plugin automation read "str: ...". An exception object that cannot be
  unpickled also makes RQ drop the job's whole meta.

Change:
- store_job_exception writes a plain dict: the type, the message, a hint
  where there is one, and a refusal's generator, sensors and automation. All
  four writers use it: the scheduling handler and fallback callback, the
  forecasting handler and the generic handler, whose comment about JSON was
  stale (meta is pickled).
- failed_job_reason renders it, appending the hint, and still reads the
  shapes stored by jobs that failed before this change.
- The asset page's jobs table formatted the stored exception itself; it now
  reads the reason through failed_job_reason, as the API and the CLI do.
- The tests that read the stored exception object, or expected "str: ..." in
  the jobs table, read the summary.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Signed-off-by: F.N. Claessen <claessen@seita.nl>

* tests: pin one failure summary on every queue

Context:
- #2696.

Change:
- A job failing on the scheduling, forecasting, reporting or ingestion queue,
  through that queue's own handler, reads as "ValueError: math domain error"
  after a fresh fetch. On main, every case fails.
- The forecasting timeout hint reaches failed_job_reason.
  On main, it fails.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Signed-off-by: F.N. Claessen <claessen@seita.nl>

* changelog: a failed job says why in the same way on every queue

Context:
- #2696.

Change:
- Bugfix entry... (continued)

Coverage Stats

34 of 35 new or added lines in 5 files covered. (97.14%)

1 existing line in 1 file now uncovered.

21305 of 24603 relevant lines covered (86.6%)

0.87 hits per line