Am 12.11.2015 um 14:36 schrieb Markus Armbruster: > Peter Maydell <peter.mayd...@linaro.org> writes: > >> [...] it's usually painful to get a >> backtrace out of this kind of qtest, because it's clearly starting >> a whole pile of QEMUs and there's no way I know of to say "only >> run a few of these tests, not the whole huge pile". > > Not sure this helps, but here goes anyway: run the make with V=1, fish > out the gtester line, add -p /name/of/the/test. Here's an example from > my shell history: > > $ MALLOC_PERTURB_=${MALLOC_PERTURB_:-$((RANDOM % 255 + 1))} gtester -k > --verbose -m=quick -p /dicts/large_dict tests/check-qjson
You can just run the test from the command line. For QTests you also need to pass a variable telling it which QEMU binary to use and since recently also which qemu-img or so. If someone has an idea how we could implement make check-qtest-<target>-<testname> or check-unit-<testname> that would be appreciated. check-qtest-<testname> would seem to collide with our wildcard handling of targets, but might be handy, too. Regards, Andreas -- SUSE Linux GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Felix Imendörffer, Jane Smithard, Graham Norton; HRB 21284 (AG Nürnberg)