Re: [seL4] Automatic testing using qemu

Thank you very much for your very interesting answer. Some issues: - I'm no longer getting output from my emulated app in the terminal. - After echoing "quit", the socket seems to be no longer read (further socat commands hang), but ps still lists qemu-system-arm. Is that expected? On 15/05/18 21:08, Matt Rice wrote:

...

Hi there,

I have written a seL4 app using CAmkES, that I am continuously building using Jenkins.

I'd like to add a test step to this continuous integration process, launching the app with qemu and parsing the output to validate my expectations.

The thing is, although all the active ("control") components reach their last instruction after a while, seL4 does not "exit" (which is expected I guess) and qemu does not stop, keeping my continuous integration job running for ever.

Any idea on how to achieve this?

Thank you very much in advance. I'd imagine there are probably a few ways, mainly by binding the monitor to some input device,

On Tue, May 15, 2018 at 7:43 AM, Paolo Crisafulli wrote: the following uses a unix socket/socat

qemu-system-i386 -monitor unix:path=./monitor.io,server,nowait & # can exit whenever with echo "system_powerdown" | socat - UNIX-CONNECT:monitor.io echo "quit" | socat - UNIX-CONNECT:monitor.io