ExternalVendorCode/genode
1
0
Fork 0
mirror of https://github.com/genodelabs/genode.git synced 2024-12-27 09:12:32 +00:00
Code Issues Actions Packages Projects Releases Wiki Activity
4b9f4d8c38
genode/repos/os/recipes/pkg/test-trace/runtime

66 lines
1.6 KiB
Plaintext
Raw Normal View History

Archive recipes for autopilot tests
2018-10-10 16:08:14 +00:00
<runtime ram="90M" caps="1000" binary="init">
<requires> <timer/> </requires>
depot_autopilot: simplify success-criterion syntax * Removes the <event> tag from all test package runtime files and replaces the contained <timeout> and <log> sub-tags with the new tags <succeed> and <fail>. If a <succeed> or <fail> tag has a content, it defines a log pattern that should be recognized and render the test failed or successful. If a <succeed> or <fail> tag has an attribute after_seconds that is not set to 0, it defines a timeout after which the test should be rendered failed or successful. * Adapts the Depot Autopilot to support the new syntax in the test-package runtime files. However, for now, the Depot Autopilot is kept compatible to the old syntax as well. If the <events> tag is present, it is prioritized over the new syntax. Fixes #4922
2023-06-24 14:57:19 +00:00
<fail after_seconds="30"/>
<succeed>child "sequence" exited with exit value 0</succeed>
<fail>Error: </fail>
Archive recipes for autopilot tests
2018-10-10 16:08:14 +00:00
<content>
<rom label="ld.lib.so"/>
<rom label="top"/>
<rom label="test-trace"/>
test-trace: test destruction of trace subjects If the trace subjects are not properly destructed when the TRACE client disappears, enabled sources will be owned by a non-existing client. In other words, when a TRACE client disappears all sources owned by the client must be disabled. genodelabs/genode#4247
2021-08-12 14:00:29 +00:00
<rom label="sequence"/>
Archive recipes for autopilot tests
2018-10-10 16:08:14 +00:00
<rom label="null"/>
</content>
<config>
<parent-provides>
<service name="ROM"/>
<service name="IRQ"/>
<service name="IO_MEM"/>
<service name="IO_PORT"/>
<service name="PD"/>
<service name="RM"/>
<service name="CPU"/>
<service name="LOG"/>
<service name="TRACE"/>
<service name="Timer"/>
</parent-provides>
<default-route>
core: filter trace subjects by TRACE session label This patch changes core's TRACE service to expose trace subjects only if their PD label matches the label of the TRACE monitor. Hence, by default, a trace monitor can only observe itself and its child components. Only if the trace monitor's parent rewrites the trace-session's label, the view of trace monitor can become broader. For example, when rewriting the trace label to an empty string "", the trace monitor becomes able to observe the sibling components hosted in the same init instance as the trace monitor. To grant a trace session the special privilege of obtaining a global system view (including the kernel's trace subjects), the top-level init has to rewrite the session's label to an empty string. At core, this specific label "init -> " is handled as a special case that discharges the filtering/namespacing of trace subjects. Note that the trace-subject label as reported as subject info is now given relative to the label of the trace session. As a nice side effect of this change, the pkg/test-trace_logger works now when executed by the depot_autopilot as well as via the test.run script. Issue #847
2023-12-01 16:52:57 +00:00
<service name="TRACE"> <parent label=""/> </service>
Archive recipes for autopilot tests
2018-10-10 16:08:14 +00:00
<any-service> <parent/> <any-child/> </any-service>
</default-route>
test-trace: test destruction of trace subjects If the trace subjects are not properly destructed when the TRACE client disappears, enabled sources will be owned by a non-existing client. In other words, when a TRACE client disappears all sources owned by the client must be disabled. genodelabs/genode#4247
2021-08-12 14:00:29 +00:00
<default caps="200"/>
<start name="sequence">
<resource name="RAM" quantum="15M"/>
Archive recipes for autopilot tests
2018-10-10 16:08:14 +00:00
<config>
test-trace: test destruction of trace subjects If the trace subjects are not properly destructed when the TRACE client disappears, enabled sources will be owned by a non-existing client. In other words, when a TRACE client disappears all sources owned by the client must be disabled. genodelabs/genode#4247
2021-08-12 14:00:29 +00:00
<start name="test-trace">
<resource name="RAM" quantum="10M"/>
<config>
core: filter trace subjects by TRACE session label This patch changes core's TRACE service to expose trace subjects only if their PD label matches the label of the TRACE monitor. Hence, by default, a trace monitor can only observe itself and its child components. Only if the trace monitor's parent rewrites the trace-session's label, the view of trace monitor can become broader. For example, when rewriting the trace label to an empty string "", the trace monitor becomes able to observe the sibling components hosted in the same init instance as the trace monitor. To grant a trace session the special privilege of obtaining a global system view (including the kernel's trace subjects), the top-level init has to rewrite the session's label to an empty string. At core, this specific label "init -> " is handled as a special case that discharges the filtering/namespacing of trace subjects. Note that the trace-subject label as reported as subject info is now given relative to the label of the trace session. As a nice side effect of this change, the pkg/test-trace_logger works now when executed by the depot_autopilot as well as via the test.run script. Issue #847
2023-12-01 16:52:57 +00:00
<trace_policy label="sequence -> test-trace" thread="test-thread" module="null"/>
test-trace: test destruction of trace subjects If the trace subjects are not properly destructed when the TRACE client disappears, enabled sources will be owned by a non-existing client. In other words, when a TRACE client disappears all sources owned by the client must be disabled. genodelabs/genode#4247
2021-08-12 14:00:29 +00:00
</config>
</start>
<start name="test-trace">
<resource name="RAM" quantum="10M"/>
<config>
core: filter trace subjects by TRACE session label This patch changes core's TRACE service to expose trace subjects only if their PD label matches the label of the TRACE monitor. Hence, by default, a trace monitor can only observe itself and its child components. Only if the trace monitor's parent rewrites the trace-session's label, the view of trace monitor can become broader. For example, when rewriting the trace label to an empty string "", the trace monitor becomes able to observe the sibling components hosted in the same init instance as the trace monitor. To grant a trace session the special privilege of obtaining a global system view (including the kernel's trace subjects), the top-level init has to rewrite the session's label to an empty string. At core, this specific label "init -> " is handled as a special case that discharges the filtering/namespacing of trace subjects. Note that the trace-subject label as reported as subject info is now given relative to the label of the trace session. As a nice side effect of this change, the pkg/test-trace_logger works now when executed by the depot_autopilot as well as via the test.run script. Issue #847
2023-12-01 16:52:57 +00:00
<trace_policy label="top" thread="ep" module="null"/>
test-trace: test destruction of trace subjects If the trace subjects are not properly destructed when the TRACE client disappears, enabled sources will be owned by a non-existing client. In other words, when a TRACE client disappears all sources owned by the client must be disabled. genodelabs/genode#4247
2021-08-12 14:00:29 +00:00
</config>
</start>
<start name="test-trace">
<resource name="RAM" quantum="10M"/>
<config>
core: filter trace subjects by TRACE session label This patch changes core's TRACE service to expose trace subjects only if their PD label matches the label of the TRACE monitor. Hence, by default, a trace monitor can only observe itself and its child components. Only if the trace monitor's parent rewrites the trace-session's label, the view of trace monitor can become broader. For example, when rewriting the trace label to an empty string "", the trace monitor becomes able to observe the sibling components hosted in the same init instance as the trace monitor. To grant a trace session the special privilege of obtaining a global system view (including the kernel's trace subjects), the top-level init has to rewrite the session's label to an empty string. At core, this specific label "init -> " is handled as a special case that discharges the filtering/namespacing of trace subjects. Note that the trace-subject label as reported as subject info is now given relative to the label of the trace session. As a nice side effect of this change, the pkg/test-trace_logger works now when executed by the depot_autopilot as well as via the test.run script. Issue #847
2023-12-01 16:52:57 +00:00
<trace_policy label="top" thread="ep" module="null"/>
test-trace: test destruction of trace subjects If the trace subjects are not properly destructed when the TRACE client disappears, enabled sources will be owned by a non-existing client. In other words, when a TRACE client disappears all sources owned by the client must be disabled. genodelabs/genode#4247
2021-08-12 14:00:29 +00:00
</config>
</start>
Archive recipes for autopilot tests
2018-10-10 16:08:14 +00:00
</config>
</start>
<start name="top">
<resource name="RAM" quantum="2M"/>
test-trace: adjust rate of top passing tracepoints The traced top instance was configured to be active every two seconds whereas the trace test uses a grace time of only 1.5 seconds before raising the FOREIGN state of a trace subject as an error. The state of a trace subject can change only whenever the traced thread passes a trace point. Hence, with the original configuration, the release of top as trace subject can take up to two seconds. The patch reduces the rate to 0.5 seconds to satisfy the expectation of test-trace.
2023-12-07 15:22:53 +00:00
<config period_ms="500"/>
Archive recipes for autopilot tests
2018-10-10 16:08:14 +00:00
</start>
</config>
</runtime>
Reference in New Issue Copy Permalink