RAMSES-2 issueshttps://gitlab.telecom-paris.fr/mbe-tools/ramses-2/-/issues2023-06-07T16:31:06Zhttps://gitlab.telecom-paris.fr/mbe-tools/ramses-2/-/issues/43Message dialog for successful RAMSES Run is not shown2023-06-07T16:31:06ZRakshit MittalMessage dialog for successful RAMSES Run is not shownAt the moment, if a RAMSES run/analysis is successful, the user is not intimated.
The user is only intimated if there is a problem with the analysis.
Some users were confused if the analysis was successful or not, because there was no me...At the moment, if a RAMSES run/analysis is successful, the user is not intimated.
The user is only intimated if there is a problem with the analysis.
Some users were confused if the analysis was successful or not, because there was no message.https://gitlab.telecom-paris.fr/mbe-tools/ramses-2/-/issues/42Requirement to have process bound to a memory seems an overshoot2021-11-11T14:00:33ZEtienne BordeRequirement to have process bound to a memory seems an overshootEtienne BordeEtienne Bordehttps://gitlab.telecom-paris.fr/mbe-tools/ramses-2/-/issues/38Dispatch_Trigger property is never used2021-04-09T13:46:04ZEtienne BordeDispatch_Trigger property is never usedWright now, all ports are considered as provoking a dispatch. If a dispatch_trigger property is used, only a subset of ports may provoke a dispatch.Wright now, all ports are considered as provoking a dispatch. If a dispatch_trigger property is used, only a subset of ports may provoke a dispatch.https://gitlab.telecom-paris.fr/mbe-tools/ramses-2/-/issues/35modal-port-connection test's trace2021-01-19T17:43:09ZOriane Salamémodal-port-connection test's tracethe expected results of the execution are not clear and need to be verifiedthe expected results of the execution are not clear and need to be verifiedOriane SalaméOriane Salaméhttps://gitlab.telecom-paris.fr/mbe-tools/ramses-2/-/issues/33timed-eventport test's execution traces2021-01-19T17:38:57ZOriane Salamétimed-eventport test's execution tracesTest execution traces on the targets linux, freertos and pok vary and should be checked.Test execution traces on the targets linux, freertos and pok vary and should be checked.Oriane SalaméOriane Salaméhttps://gitlab.telecom-paris.fr/mbe-tools/ramses-2/-/issues/32Locks with ICPP policy is not implemented2021-01-19T13:22:54ZEtienne BordeLocks with ICPP policy is not implementedEtienne BordeEtienne Bordehttps://gitlab.telecom-paris.fr/mbe-tools/ramses-2/-/issues/30Add integration test with Dispatch_Offset2021-01-12T12:47:23ZEtienne BordeAdd integration test with Dispatch_OffsetEtienne BordeEtienne Bordehttps://gitlab.telecom-paris.fr/mbe-tools/ramses-2/-/issues/21add a user_defined_config field to thread_config_t2020-12-29T15:23:46ZEtienne Bordeadd a user_defined_config field to thread_config_thttps://gitlab.telecom-paris.fr/mbe-tools/ramses-2/-/issues/20Add an example with error management2020-12-30T14:45:19ZEtienne BordeAdd an example with error managementEtienne BordeEtienne Bordehttps://gitlab.telecom-paris.fr/mbe-tools/ramses-2/-/issues/17Add validation rule to make sure classifiers referenced as entrypoint (init, ...2021-01-11T17:11:43ZEtienne BordeAdd validation rule to make sure classifiers referenced as entrypoint (init, activation, etc.) have no featureEtienne BordeEtienne Borde