lp1153769 in ubuntu_cts_kernel failed on P with logfd error

Bug #1801877 reported by Po-Hsu Lin
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
ubuntu-kernel-tests
Confirmed
Undecided
Unassigned
linux (Ubuntu)
Incomplete
Undecided
Unassigned
Nominated for Precise by Po-Hsu Lin

Bug Description

If you run it on jenkins remotely:
~/kernel-testing/remote --kernel-test-list=ubuntu_cts_kernel ubuntu@rizzo

It will fail with:
 *** lp1153769 ***
 Running '/home/ubuntu/autotest/client/tests/ubuntu_cts_kernel/bugs/lp1153769 eno1'
 [stderr] Failed opening logfd: Invalid argument
 Exception escaping from test:
Traceback (most recent call last):
  File "/home/ubuntu/autotest/client/shared/test.py", line 411, in _exec
    _call_test_function(self.execute, *p_args, **p_dargs)
  File "/home/ubuntu/autotest/client/shared/test.py", line 823, in _call_test_function
    return func(*args, **dargs)
  File "/home/ubuntu/autotest/client/shared/test.py", line 291, in execute
    postprocess_profiled_run, args, dargs)
  File "/home/ubuntu/autotest/client/shared/test.py", line 212, in _call_run_once
    self.run_once(*args, **dargs)
  File "/home/ubuntu/autotest/client/tests/ubuntu_cts_kernel/ubuntu_cts_kernel.py", line 37, in run_once
    self.results = utils.system_output(cmd, retain_output=True)
  File "/home/ubuntu/autotest/client/shared/utils.py", line 1267, in system_output
    verbose=verbose, args=args).stdout
  File "/home/ubuntu/autotest/client/shared/utils.py", line 918, in run
    "Command returned non-zero exit status")
CmdError: Command </home/ubuntu/autotest/client/tests/ubuntu_cts_kernel/bugs/lp1153769 eno1> failed, rc=234, Command returned non-zero exit status
* Command:
    /home/ubuntu/autotest/client/tests/ubuntu_cts_kernel/bugs/lp1153769 eno1
Exit status: 234
Duration: 0.056932926178

This can be reproduced with just ssh on the host to SUT:
$ myssh rizzo "/home/ubuntu/autotest/client/tests/ubuntu_cts_kernel/bugs/lp1153769 eno1"
Warning: Permanently added 'rizzo,10.246.72.30' (ECDSA) to the list of known hosts.
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.ubuntu.com/ubuntu/autotest-client-tests
git clone --depth=1 git://kernel.ubuntu.com/ubuntu/autotest
rm -fr autotest/client/tests
ln -sf ~/autotest-client-tests autotest/client/tests
AUTOTEST_PATH=/home/ubuntu/autotest sudo -E autotest/client/autotest-local --verbose autotest/client/tests/ubuntu_cts_kernel/control

Or just run the test directly on the SUT:
$ /home/ubuntu/autotest/client/tests/ubuntu_cts_kernel/bugs/lp1153769 eno1
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://lore.kernel.org/patchwork/patch/309039/

Po-Hsu Lin (cypressyew)
Changed in ubuntu-kernel-tests:
status: New → Confirmed
description: updated
Revision history for this message
Po-Hsu Lin (cypressyew) wrote :

Targeting linux-tools-common Precise package as it's where the perf tool came from.

Revision history for this message
Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote : Missing required logs.

This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:

apport-collect 1801877

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

Changed in linux (Ubuntu):
status: New → Incomplete
Brad Figg (brad-figg)
tags: added: cscc
Po-Hsu Lin (cypressyew)
tags: added: ubuntu-cts-kernel
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.