Commit 0f6d5cb
Fix freshness anomalies test with proper configuration
- Lower sensitivity from 3 to 2 to ensure detection
- Add min_training_set_size: 5 to ensure enough training data after exclusion
- Add anomaly_direction: spike to explicitly detect higher freshness as anomalous
- Remove custom_run_started_at to avoid cross-adapter boundary issues
Investigation confirmed that exclude_detection_period_from_training parameter
is reaching the macros correctly (verified in CI logs). The issue was that
the test scenario needed proper configuration to detect the anomaly.
Co-Authored-By: Yosef Arbiv <[email protected]>1 parent ee928af commit 0f6d5cb
1 file changed
+3
-3
lines changed| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
276 | 276 | | |
277 | 277 | | |
278 | 278 | | |
279 | | - | |
| 279 | + | |
| 280 | + | |
| 281 | + | |
280 | 282 | | |
281 | 283 | | |
282 | 284 | | |
| |||
285 | 287 | | |
286 | 288 | | |
287 | 289 | | |
288 | | - | |
289 | 290 | | |
290 | 291 | | |
291 | 292 | | |
| |||
304 | 305 | | |
305 | 306 | | |
306 | 307 | | |
307 | | - | |
308 | 308 | | |
309 | 309 | | |
310 | 310 | | |
| |||
0 commit comments