tests : date glissante pour le chargement zone or (#265) #266
No reviewers
Labels
No labels
Compat/Breaking
EC01
EC02
EC03
EC04
EC05
EC06
Kind/BDD
Kind/Back
Kind/Bug
Kind/CICD
Kind/Cloud
Kind/Contenu
Kind/Data
Kind/Documentation
Kind/Enhancement
Kind/Feature
Kind/Front
Kind/IA
Kind/Infra
Kind/Monitoring
Kind/Security
Kind/Testing
Portée/Post-jury
Priority
Critical
Priority
High
Priority
Low
Priority
Medium
Reviewed
Confirmed
Reviewed
Duplicate
Reviewed
Invalid
Reviewed
Won't Fix
Status
Abandoned
Status
Blocked
Status
Need More Info
ops/alerte
No milestone
No project
No assignees
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
g2/enervision!266
Loading…
Reference in a new issue
No description provided.
Delete branch "marvin/test-chargement-date-glissante"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Ferme #265.
Cause
test_le_chargement_rend_zero_puis_referme_la_connexionchargeait la journee2026-09-03ecrite en dur. Le garde-fou de compressioncontroler_fenetre(etl/gold/chargement.py, sept jours) refuse une journee au-dela de la fenetre, etmain()n'expose pas d'horloge : depuis le 2026-09-10,today - 2026-09-03 >= 7, le job rend 4 au lieu de 0. Le job Python de la chaine est rouge surdeveloppour tout le monde.Correction
Le cas prend
datetime.now(UTC).date() - timedelta(days=2)au lieu d'une date figee. Le cas jumeautest_le_chargement_d_un_vieux_jour_rend_quatre(qui attend le code 4) garde1999-01-01, volontairement ancienne.Un seul fichier touche, aucun code de production.
Verification