You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This ticket follows yesterday's discussion about having one analytics session for all profiles that are part of the same executing session from any RCT. For example, an application is executed using EnTK with profiling enabled. This should trigger RP's profiles, which in turn should trigger SAGA profiles.
Furthermore, the analytics session of this application should include all profiles and show the component hierarchy. For instance, when we are doing:
This ticket follows yesterday's discussion about having one analytics session for all profiles that are part of the same executing session from any RCT. For example, an application is executed using
EnTK
with profiling enabled. This should triggerRP
's profiles, which in turn should triggerSAGA
profiles.Furthermore, the analytics session of this application should include all profiles and show the component hierarchy. For instance, when we are doing:
should include all timing from all levels below
EnTK
.That should also be true for the frameworks, systems that use
EnTK
, i.e. HTBAC, RepEx, ICEBERG.The text was updated successfully, but these errors were encountered: