Public bug reported:

This issue can be reproduced in 3.13.0-142 in proposed and 3.13.0-141.
So it should not be considered as a regression.

We didn't have this issue before, until I'm testing 3.13 Precise LTS
kernel on the systems (201307-13930 - i386 and 201308-14073 - amd64) in
Cert lab instead of using our regular regression-testing test pool from
kernel team this cycle.

All btrfs related tests in ubuntu_ecryptfs failed.

The output is not really helpful, it's just saying that the return value is 1, 
03:37:47 DEBUG| Running 'tests/ -K -t -b 
1000000 -D /mnt/image -l /mnt/lower -u /mnt/upper -f btrfs'
03:37:59 ERROR| Exception escaping from test:
Traceback (most recent call last):
  File "/home/ubuntu/autotest/client/shared/", line 411, in _exec
    _call_test_function(self.execute, *p_args, **p_dargs)
  File "/home/ubuntu/autotest/client/shared/", line 823, in 
    return func(*args, **dargs)
  File "/home/ubuntu/autotest/client/shared/", line 291, in execute
    postprocess_profiled_run, args, dargs)
  File "/home/ubuntu/autotest/client/shared/", line 212, in 
    self.run_once(*args, **dargs)
  File "/home/ubuntu/autotest/client/tests/ubuntu_ecryptfs/", 
line 45, in run_once
    self.results = utils.system_output(cmd, retain_output=True)
  File "/home/ubuntu/autotest/client/shared/", line 1267, in 
    verbose=verbose, args=args).stdout
  File "/home/ubuntu/autotest/client/shared/", line 918, in run
    "Command returned non-zero exit status")
CmdError: Command <tests/ -K -t -b 1000000 -D 
/mnt/image -l /mnt/lower -u /mnt/upper -f btrfs> failed, rc=1, Command returned 
non-zero exit status
* Command: 
    tests/ -K -t -b 1000000 -D /mnt/image -l
    /mnt/lower -u /mnt/upper -f btrfs
Exit status: 1
Duration: 12.1887788773

** Affects: linux (Ubuntu)
     Importance: Undecided
         Status: Incomplete

** Tags: amd64 i386 precise

You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

  btrfs related tests in ubuntu_ecryptfs failed on Precise amd64 / i386

To manage notifications about this bug go to:

ubuntu-bugs mailing list

Reply via email to