ubuntu_kvm_unit tests fail with exeception after intel-iommu.c

Bug #1814567 reported by Sean Feole on 2019-02-04
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
ubuntu-kernel-tests
Undecided
Unassigned

Bug Description

The ubuntu_kvm_unit tests all appear to fail across all instance types during the runtime of the kvm_unit tests. It's a fairly vanilla msg, theres no output of value initially. It would appear that whatever runs after intel-iommu is making this throw an exception.

Logs for Bionic

231. 01/23 21:15:50 DEBUG| utils:0153| [stdout] TESTNAME=hyperv_clock TIMEOUT=90s ACCEL= ./x86/run x86/hyperv_clock.flat -smp 2 -cpu kvm64,hv_time
232. 01/23 21:15:51 DEBUG| utils:0153| [stdout] FAIL hyperv_clock
233. 01/23 21:15:51 DEBUG| utils:0153| [stdout] TESTNAME=intel_iommu TIMEOUT=30 ACCEL= ./x86/run x86/intel-iommu.flat -smp 4 -M q35,kernel-irqchip=split -device intel-iommu,intremap=on,eim=off -device edu
234. 01/23 21:15:52 DEBUG| utils:0153| [stdout] PASS intel_iommu (11 tests)
235. 01/23 21:15:52 ERROR| test:0414| Exception escaping from test:
236. Traceback (most recent call last):
237. File "/home/ubuntu/autotest/client/shared/test.py", line 411, in _exec
238. _call_test_function(self.execute, *p_args, **p_dargs)
239. File "/home/ubuntu/autotest/client/shared/test.py", line 823, in _call_test_function
240. return func(*args, **dargs)
241. File "/home/ubuntu/autotest/client/shared/test.py", line 291, in execute
242. postprocess_profiled_run, args, dargs)
243. File "/home/ubuntu/autotest/client/shared/test.py", line 212, in _call_run_once
244. self.run_once(*args, **dargs)
245. File "/home/ubuntu/autotest/client/tests/ubuntu_kvm_unit_tests/ubuntu_kvm_unit_tests.py", line 82, in run_once
246. raise error.TestError('Test error, check debug logs for complete test output')
247. TestError: Test error, check debug logs for complete test output

Sean Feole (sfeole) wrote :
Sean Feole (sfeole) wrote :

It would appear after looking closer that there are indeed 2x separate failures for Xenial and Bionic, both occuring at different points in time runing the tests, however all of the instance types in the series will fail at the same point.
Again, same type of failure, rather vague... the test will need to be run by hand in order to identify it, as the logs did not record the crash dump.

 01/25 04:35:46 DEBUG| utils:0153| [stdout] SKIP intel_iommu (qemu-system-x86_64: Invalid parameter type for 'kernel-irqchip', expected: boolean)
227. 01/25 04:35:46 ERROR| test:0414| Exception escaping from test:
228. Traceback (most recent call last):
229. File "/home/ubuntu/autotest/client/shared/test.py", line 411, in _exec
230. _call_test_function(self.execute, *p_args, **p_dargs)
231. File "/home/ubuntu/autotest/client/shared/test.py", line 823, in _call_test_function
232. return func(*args, **dargs)
233. File "/home/ubuntu/autotest/client/shared/test.py", line 291, in execute
234. postprocess_profiled_run, args, dargs)
235. File "/home/ubuntu/autotest/client/shared/test.py", line 212, in _call_run_once
236. self.run_once(*args, **dargs)
237. File "/home/ubuntu/autotest/client/tests/ubuntu_kvm_unit_tests/ubuntu_kvm_unit_tests.py", line 82, in run_once
238. raise error.TestError('Test error, check debug logs for complete test output')
239. TestError: Test error, check debug logs for complete test output
240.

description: updated
Sean Feole (sfeole) wrote :

Above logs for Xenial

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers

Bug attachments