-
Notifications
You must be signed in to change notification settings - Fork 46
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
core: stdcm: stop computing engineering allowances during exploration #7090
Conversation
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## dev #7090 +/- ##
============================================
- Coverage 28.31% 28.28% -0.04%
+ Complexity 2250 2229 -21
============================================
Files 1090 1090
Lines 136477 136492 +15
Branches 2745 2737 -8
============================================
- Hits 38647 38608 -39
- Misses 96233 96290 +57
+ Partials 1597 1594 -3
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
ae53f73
to
83ce5fa
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Up to this point, LGTM. The 20_000
value after which we consider that any given margin can be added is an annoying but required value here.
i.e. if we use a resource from t=42 to t=84, the conflict time can't start before t=42, even if the resource has been scheduled for longer
83ce5fa
to
bad2105
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ok for the tests parts :)
Fix #6985
The main change is that we don't actually compute engineering allowance during the exploration anymore. But that highlights all the subtle bugs we have around, especially in the post-processing, so it also includes some bugfixes.