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/41Duplicate pok_kernel_error in generated code2021-11-11T13:59:56ZEtienne BordeDuplicate pok_kernel_error in generated codeEtienne BordeEtienne Bordehttps://gitlab.telecom-paris.fr/mbe-tools/ramses-2/-/issues/40Filter issue for paramater connections in thread2021-11-10T14:02:37ZEtienne BordeFilter issue for paramater connections in threadEtienne BordeEtienne Bordehttps://gitlab.telecom-paris.fr/mbe-tools/ramses-2/-/issues/39Missing Base_Types in with clauses2021-11-10T14:01:09ZEtienne BordeMissing Base_Types in with clausesEtienne 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/12Add integration tests for FreeRTOS target2021-03-04T08:27:38ZEtienne BordeAdd integration tests for FreeRTOS targetOriane SalaméOriane Salaméhttps://gitlab.telecom-paris.fr/mbe-tools/ramses-2/-/issues/24Delete task semaphores when stopping the task2021-02-11T21:10:54ZEtienne BordeDelete task semaphores when stopping the taskOriane SalaméOriane Salaméhttps://gitlab.telecom-paris.fr/mbe-tools/ramses-2/-/issues/4BA subclauses resolution fails when chaining transformations2021-02-11T21:10:46ZEtienne BordeBA subclauses resolution fails when chaining transformationsDominique BlouinDominique Blouinhttps://gitlab.telecom-paris.fr/mbe-tools/ramses-2/-/issues/36Close sockets properly when terminating processes2021-02-11T21:10:26ZEtienne BordeClose sockets properly when terminating processeshttps://gitlab.telecom-paris.fr/mbe-tools/ramses-2/-/issues/37Handling ACTIVE_THREAD_HANDLING_PROTOCOL property2021-02-11T08:31:42ZOriane SalaméHandling ACTIVE_THREAD_HANDLING_PROTOCOL propertyProperty ACTIVE_THREAD_HANDLING_PROTOCOL must be taken into account in the model.Property ACTIVE_THREAD_HANDLING_PROTOCOL must be taken into account in the model.Etienne BordeEtienne Bordehttps://gitlab.telecom-paris.fr/mbe-tools/ramses-2/-/issues/28Only add -lpthread -lrt options in generated makefile if target is posix-like...2021-01-26T13:54:53ZEtienne BordeOnly add -lpthread -lrt options in generated makefile if target is posix-like (linux, ev3dev, freertos with posix port)Etienne BordeEtienne Bordehttps://gitlab.telecom-paris.fr/mbe-tools/ramses-2/-/issues/25Extend possible Portable_Architecture values for FreeRTOS configuration2021-01-26T12:39:27ZEtienne BordeExtend possible Portable_Architecture values for FreeRTOS configurationOriane SalaméOriane Salaméhttps://gitlab.telecom-paris.fr/mbe-tools/ramses-2/-/issues/34shared-resources test2021-01-22T14:31:42ZOriane Salaméshared-resources testshared-resources test should be documented (segfault on freertos due to a mutex non-initialization)shared-resources test should be documented (segfault on freertos due to a mutex non-initialization)Etienne BordeEtienne Bordehttps://gitlab.telecom-paris.fr/mbe-tools/ramses-2/-/issues/31Remove references to start_time when computing dispatch_time (absolute time i...2021-01-19T20:26:54ZEtienne BordeRemove references to start_time when computing dispatch_time (absolute time including start_time remains consistent for dates comparison)Etienne BordeEtienne Bordehttps://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/29Add EV3DEV to integration all workflow2021-01-11T18:19:40ZEtienne BordeAdd EV3DEV to integration all workflowEtienne BordeEtienne Borde