genode/base/run/cap_integrity.run
Stefan Kalkowski bb90a2d41d Let cap_integrity test be more expressive
By using the `compare_output_to` method from the run tool instead of using
regexp in the cap_integrity run-script, the test outputs the undesired lines
instead of just signaling that the test failed.
2012-03-23 14:34:09 +01:00

37 lines
801 B
Plaintext

build "core init test/cap_integrity"
create_boot_directory
install_config {
<config>
<parent-provides>
<service name="ROM"/>
<service name="RAM"/>
<service name="CPU"/>
<service name="RM"/>
<service name="CAP"/>
<service name="PD"/>
<service name="SIGNAL"/>
<service name="LOG"/>
</parent-provides>
<default-route>
<any-service> <parent/> </any-service>
</default-route>
<start name="test-cap_integrity">
<resource name="RAM" quantum="10M"/>
</start>
</config>
}
build_boot_image "core init test-cap_integrity"
append qemu_args "-nographic -m 64"
# increase expect buffer size, since there might be many log messages
match_max -d 100000
run_genode_until {child exited with exit value 0.*} 60
grep_output {\[init\] test message}
compare_output_to { }