lp1153769 in ubuntu_cts_kernel failed on P with logfd error
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
ubuntu-kernel-tests |
Confirmed
|
Undecided
|
Unassigned | ||
linux (Ubuntu) |
Incomplete
|
Undecided
|
Unassigned | ||
Bug Description
If you run it on jenkins remotely:
~/kernel-
It will fail with:
*** lp1153769 ***
Running '/home/
[stderr] Failed opening logfd: Invalid argument
Exception escaping from test:
Traceback (most recent call last):
File "/home/
_call_
File "/home/
return func(*args, **dargs)
File "/home/
postprocess
File "/home/
self.
File "/home/
self.results = utils.system_
File "/home/
verbose=
File "/home/
"Command returned non-zero exit status")
CmdError: Command </home/
* Command:
/home/
Exit status: 234
Duration: 0.056932926178
This can be reproduced with just ssh on the host to SUT:
$ myssh rizzo "/home/
Warning: Permanently added 'rizzo,
Failed opening logfd: Invalid argument
But if you run this test locally on the SUT, it will pass without any issue:
sudo apt-get install git python-minimal gdb -y
git clone --depth=1 git://kernel.
git clone --depth=1 git://kernel.
rm -fr autotest/
ln -sf ~/autotest-
AUTOTEST_
Or just run the test directly on the SUT:
$ /home/ubuntu/
autotest kernel-test-results kernel-testing
Performance counter stats for 'ls':
2222256 cycles # 0.000 GHz
0.002389283 seconds time elapsed
I think this has something to do with the perf command and the shell redirection:
https:/
Changed in ubuntu-kernel-tests: | |
status: | New → Confirmed |
description: | updated |
tags: | added: cscc |
tags: | added: ubuntu-cts-kernel |
Targeting linux-tools-common Precise package as it's where the perf tool came from.