Fix method dispatchQ #227
Merged
Fix method dispatchQ #227
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…help fixing issue 218 Build should fail with this message (issue 218) [ERROR] Failures: [ERROR] LfBusImplTest.updateGeneratorsStateTest:93 sum of generators calculatedQ should be equals to qToDispatch ==> expected: <-6.412103131789854> but was: <-7.4807869870881625> Signed-off-by: Fabien Rigaux <fabien.rigaux@free.fr>
Signed-off-by: Anne Tilloy <anne.tilloy@rte-france.com>
annetill
changed the title
Signed-off-by: Anne Tilloy <anne.tilloy@rte-france.com>
|
Kudos, SonarCloud Quality Gate passed! |
geofjamg
approved these changes
Mar 2, 2021
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Please check if the PR fulfills these requirements (please use
'[x]'to check the checkboxes, or submit the PR and then click the checkboxes)Does this PR already have an issue describing the problem ? If so, link to this issue using
'#XXX'and skip the rest#218
Before trying to make test running successfull, we should check that 218 is really an issue.
What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)
Build failure according to issue 218