Quantal kernel tests hang on autotest/client/tools/glue_testsuites with 3.5.0-26.42 on an intel_64-mga_g200ew machine

[Para Siva]

On an intel-64 bit machine, (Alkaid) the tests hang on the following step and fail to proceed further

autotest/client/tools/glue_testsuites /tmp/workspace/autotest-results.ubuntu_ecryptfs.xml /tmp/workspace/autotest-results.ubuntu_qrt_apparmor.xml /tmp/workspace/autotest-results.ubuntu_qrt_kernel_aslr_collisions.xml /tmp/workspace/autotest-results.ubuntu_qrt_kernel_hardening.xml /tmp/workspace/autotest-results.ubuntu_qrt_kernel_panic.xml /tmp/workspace/autotest-results.ubuntu_qrt_kernel_security.xml

This happens almost once in every two runs.

Though not sure how relevant it is but I see this message in dmesg
       init: failsafe main process (601) killed by TERM signal

https://jenkins.qa.ubuntu.com/view/SRU%20Kernel/job/sru_kernel-quantal-generic_i386-intel_64-mga_g200ew/34/consoleText is one of such jobs.

[Brad Figg (brad-figg)]

@psivaa,

Just for information sake, that is a python script that takes the data from the various, individual, tests and combines them into one result. This is not a kernel bug but a kernel, testing, infrastructure issue.

[Po-Hsu Lin (cypressyew)]

Quantal EOL, closing this bug.