On 03.11.2017 10:51, no-re...@patchew.org wrote: > Hi, > > This series failed automatic build test. Please find the testing commands and > their output below. If you have docker installed, you can probably reproduce > it > locally. [...] > GTESTER tests/test-coroutine > GTESTER tests/test-visitor-serialization > GTESTER tests/test-aio > GTESTER tests/test-iov > GTESTER tests/test-aio-multithread > GTESTER tests/test-throttle > GTESTER tests/test-thread-pool > GTESTER tests/test-hbitmap > GTESTER tests/test-blockjob-txn > GTESTER tests/test-blockjob > GTESTER tests/test-x86-cpuid > GTESTER tests/test-xbzrle > GTESTER tests/test-vmstate > Failed to load simple/primitive:b_1 > Failed to load simple/primitive:i64_2 > Failed to load simple/primitive:i32_1 > Failed to load simple/primitive:i32_1 > Failed to load test/with_tmp:a > Failed to load test/tmp_child_parent:f > Failed to load test/tmp_child:parent > Failed to load test/with_tmp:tmp > Failed to load test/tmp_child:diff > Failed to load test/with_tmp:tmp > Failed to load test/tmp_child:diff > Failed to load test/with_tmp:tmp > GTESTER tests/test-cutils > GTESTER tests/test-shift128 > GTESTER tests/test-mul64 > GTESTER tests/test-int128 > GTESTER tests/rcutorture > GTESTER tests/test-rcu-list > GTESTER tests/test-qdist > GTESTER tests/test-qht > GTester: last random seed: R02S7edfc183e8c228b3f1f73d7b19921a84 > LINK tests/test-qht-par > GTESTER tests/test-bitops > GTESTER tests/test-bitcnt > GTESTER tests/check-qom-interface > GTESTER tests/check-qom-proplist > GTESTER tests/test-qemu-opts > GTESTER tests/test-keyval > GTESTER tests/test-write-threshold > GTESTER tests/test-crypto-hash > GTESTER tests/test-crypto-hmac > GTESTER tests/test-crypto-cipher > GTESTER tests/test-crypto-secret > GTESTER tests/test-qga > GTESTER tests/test-timed-average > GTESTER tests/test-io-task > GTESTER tests/test-io-channel-socket > GTESTER tests/test-io-channel-file > GTESTER tests/test-io-channel-command > GTESTER tests/test-io-channel-buffer > GTESTER tests/test-base64 > GTESTER tests/test-crypto-ivgen > GTESTER tests/test-crypto-afsplit > GTESTER tests/test-crypto-xts
Mhh, this looks somewhat strange - apparently the test-crypto-block has now been skipped - but then I wonder why this was working before here if the crypto libraries were not available? ... maybe there's still something wrong with my patch? > GTESTER tests/test-logging > GTESTER tests/test-replication > GTESTER tests/test-bufferiszero > GTESTER tests/test-uuid > GTESTER tests/ptimer-test > GTESTER tests/test-qapi-util > GTESTER check-qtest-x86_64 > GTESTER check-qtest-aarch64 > GTESTER tests/test-qobject-output-visitor > GTESTER tests/test-clone-visitor > GTESTER tests/test-qobject-input-visitor > GTESTER tests/test-qmp-commands > GTESTER tests/test-string-input-visitor > GTESTER tests/test-string-output-visitor > GTESTER tests/test-qmp-event > GTESTER tests/test-opts-visitor > GTESTER tests/test-qht-par > make: *** [check-tests/test-aio-multithread] Error 1 > make: *** Waiting for unfinished jobs.... > Could not access KVM kernel module: No such file or directory > qemu-system-x86_64: failed to initialize KVM: No such file or directory > qemu-system-x86_64: Back to tcg accelerator ... but this test-aio-multithread error is certainly not related to my patch, I think. Is this already a known issue? Thomas
