Opened 8 years ago
Last modified 7 years ago
#3937 new defect
ScalableTestSuite...OneGeneratorStepLoad fails for IDA solver
Reported by: | Henning Kiel | Owned by: | somebody |
---|---|---|---|
Priority: | critical | Milestone: | Future |
Component: | Run-time | Version: | |
Keywords: | Cc: | Francesco Casella, Willi Braun |
Description
ScalableTestSuite.Power.ConceptualPowerSystem.Verification.OneGeneratorStepLoad fails since run of ScalableTestSuite on 2016-05-25 (was OK on 2016-05-22)
Error message in simulation is:
stdout | info | Maximum number of event iterations changed to 400 *** Error in `./ScalableTestSuite.Power.ConceptualPowerSystem.Verification.OneGeneratorStepLoad': realloc(): invalid old size: 0x00000000011d89a0 *** Aborted
Change History (8)
comment:1 by , 8 years ago
Cc: | added |
---|
comment:2 by , 8 years ago
comment:3 by , 8 years ago
Willi Braun started the two library coverage tests of May 25th using the IDA solver, as you can see from the flags. There is probably still something wrong with the solver implementation
comment:4 by , 8 years ago
Cc: | added |
---|---|
Priority: | blocker → high |
Summary: | ScalableTestSuite.Power.ConceptualPowerSystem.Verification.OneGeneratorStepLoad fails → ScalableTestSuite...OneGeneratorStepLoad fails for IDA solver |
comment:5 by , 8 years ago
Priority: | high → critical |
---|
I don't want to start a priority war, and yes, blocker was too much, but we cannot really release a solver that has this kind of basic problems.
comment:7 by , 8 years ago
Milestone: | 1.11.0 → 1.12.0 |
---|
Milestone moved to 1.12.0 due to 1.11.0 already being released.
comment:8 by , 7 years ago
Milestone: | 1.12.0 → Future |
---|
The milestone of this ticket has been reassigned to "Future".
If you think the issue is still valid and relevant for you, please select milestone 1.13.0 for back-end, code generation and run-time issues, or 2.0.0 for front-end issues.
If you are aware that the problem is no longer present, please select the milestone corresponding to the version of OMC you used to check that, and set the status to "worksforme".
In both cases, a short informative comment would be welcome.
I cannot reproduce this error on OSX. Total used memory is 0.625GB.
Maybe the problem is some kind of out-of-memory error that is not handled correctly, as there are plenty of simulations running in parallel on the test server?