dml-solving issueshttps://gitlab2.informatik.uni-wuerzburg.de/descartes/dml-solving/-/issues2018-05-18T11:10:32+02:00https://gitlab2.informatik.uni-wuerzburg.de/descartes/dml-solving/-/issues/58QPN validation throws error but model can be analyzed2018-05-18T11:10:32+02:00Ghost UserQPN validation throws error but model can be analyzedModel validation in DML2QPN class throws an exception when using a delay user action. If commented out, analysis works as intended.
private void validateModel(EObject modelRoot) {
Diagnostic diagnostic = Diagnostician.INSTANC...Model validation in DML2QPN class throws an exception when using a delay user action. If commented out, analysis works as intended.
private void validateModel(EObject modelRoot) {
Diagnostic diagnostic = Diagnostician.INSTANCE.validate(modelRoot);
if (diagnostic.getSeverity() != Diagnostic.OK) {
throw new IllegalStateException(diagnostic.getMessage()); <=======
}
}https://gitlab2.informatik.uni-wuerzburg.de/descartes/dml-solving/-/issues/16Assertion failure when solving model with coarse-grained behavior2017-08-18T13:16:10+02:00Chair of Software EngineeringAssertion failure when solving model with coarse-grained behaviorSee attached model.
Log message:
```
Starting dml2qpn transformation
configuration: transformation errors are FATAL
configuration: NOT processing linking resources
configuration: 0.0 simulated seconds warmup period
configuration: 0.0 s...See attached model.
Log message:
```
Starting dml2qpn transformation
configuration: transformation errors are FATAL
configuration: NOT processing linking resources
configuration: 0.0 simulated seconds warmup period
configuration: 0.0 simulated seconds total run length
Input instance size:
1 UsageScenarios
1 SystemCallUserActions
0 usagemodel Loops
0 usagemodel Branches
3 AssemblyContexts
3 referenced BasicComponents
0 referenced CompositeComponents
0 referenced SubSystems
3 referenced RepositoryComponents in total
0 referenced ExternalCallActions
0 referenced LoopActions
0 referenced BranchActions
0 referenced ForkActions
0 referenced InternalActions
0 referenced AcquireActions
0 referenced ReleaseActions
For name place_measurement_for_UsageScenario_name:Main_id:_P31PILC6EeSswLEOHh4nHw, no object could be found in the map.
For name place_system_call_user_action_entry_BasicComponent_name:/wildfly-ejb-multi-server-app-web_id:_kZogcbDUEeSuULeVnXCMbQ//CoarseGrainedBehavior, no object could be found in the map.
For name place_system_call_user_action_exit_BasicComponent_name:/wildfly-ejb-multi-server-app-web_id:_kZogcbDUEeSuULeVnXCMbQ//CoarseGrainedBehavior, no object could be found in the map.
For name place_loop_pool_BasicComponent_name:/wildfly-ejb-multi-server-app-web_id:_kZogcbDUEeSuULeVnXCMbQ//CoarseGrainedBehavior//ExternalCallFrequency, no object could be found in the map.
ASSERT [warning] failed at (dml2qpn.qvto:1411) : There was already a place with name place_coarsegrainedbehavior_externalcallfrequency_connector_BasicComponent_name:/wildfly-ejb-multi-server-app-web_id:_kZogcbDUEeSuULeVnXCMbQ//CoarseGrainedBehavior//ExternalCallFrequency
For name queue_container_ComputingInfrastructure_name:app-web_id:_kQDGoLDUEeSPupq0TAdjVQ_resourcetype_ProcessingResourceType_name:CPU_id:_3ql5IJB4EeKmfoqNH_-HEA, no object could be found in the map.
Terminating execution...
```https://gitlab2.informatik.uni-wuerzburg.de/descartes/dml-solving/-/issues/9Implemented model composition step may 'truncate' requested probes2017-08-18T13:16:03+02:00Chair of Software EngineeringImplemented model composition step may 'truncate' requested probesThe current implementation of the model composition step (see <code>edu.kit.ipd.descartes.solving.tailoring.TailoredModelComposition</code>) may 'truncate' requested probes.
For example:
If the default service behavior abstraction leve...The current implementation of the model composition step (see <code>edu.kit.ipd.descartes.solving.tailoring.TailoredModelComposition</code>) may 'truncate' requested probes.
For example:
If the default service behavior abstraction level is set to black box, and there is a service with two service behavior abstractions (fine- or) coarse-grained and black box,
the black box behavior will get selected even if there were, e.g., some resource utilization probes that would have been affected by the (fine- or) coarse-grained behavior, but are not affected by the black box behavior.
See Fabian's PhD for a model composition algorithm, that takes such potential conflicts into account.https://gitlab2.informatik.uni-wuerzburg.de/descartes/dml-solving/-/issues/7Plug-in tests in edu.kit.ipd.descartes.solving.transformations.dmm2qpn.test d...2017-08-18T13:16:01+02:00Chair of Software EngineeringPlug-in tests in edu.kit.ipd.descartes.solving.transformations.dmm2qpn.test do not run on build serverThe tests in edu.kit.ipd.descartes.solving.transformations.dmm2qpn.test have to be run as JUnit plug-in tests.
While the tests are valid in the Eclipse workspace, running the tests during the maven build fails.
The current build configu...The tests in edu.kit.ipd.descartes.solving.transformations.dmm2qpn.test have to be run as JUnit plug-in tests.
While the tests are valid in the Eclipse workspace, running the tests during the maven build fails.
The current build configuration skips the tests in edu.kit.ipd.descartes.solving.transformations.dmm2qpn.test