admin/goodwe-addon
1
0
Fork 0
Code Issues Pull Requests 1 Actions Packages Projects Releases Wiki Activity

CI-12: test_tariff.py no longer says CI cannot see the infra repo
checks / unit (pull_request) Successful in 8m47s
Details
infra-pin / fresh (pull_request) Successful in 1s
Details

Browse Source 
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
glenn schrooyen
2026-09-25 17:27:06 +02:00
co-authored by Claude Opus 5.5
parent d0891a6bca
commit c493a6d67a
1 changed files with 3 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files
goodwe_controller/test_tariff.py
+3 -3
View File
@@ -90,9 +90,9 @@ guard has to improve on, which is the useful thing a 2-day replay can say.
The two days are committed here as `scenarios/p1-net-<date>.jsonl.gz` The two days are committed here as `scenarios/p1-net-<date>.jsonl.gz`
(`{"t": iso8601, "w": signed_watts}` per line, derived from the HA recorder (`{"t": iso8601, "w": signed_watts}` per line, derived from the HA recorder
export) for the reason `scenarios/p1-age-2026-08-26.jsonl.gz` already is: the export), as `scenarios/p1-age-2026-08-26.jsonl.gz` already is. When they were
infra repo is private, CI's token is minted for this repository only, and a committed, CI could not see the infra repo; since CI-12 it checks admin/goodwe
regression fixture that CI cannot see is not a regression fixture. out at `.gitea/infra-pin`, but these fixtures stay here with the tests.
The recorder's window rolls: 2026-08-01 leaves it around 2026-09-15, which is The recorder's window rolls: 2026-08-01 leaves it around 2026-09-15, which is
why the committed copy is the artefact and not the API call. why the committed copy is the artefact and not the API call.