Public bug reported:

Reproduce rate 5 out of 5.

This issue failed frequently on this node, and can be seen on older 4.13 kernel.
And this test can pass on the other node. so that this should not be considered 
as a regression in this cycle.
 
Steps:
1. Deploy an Artful system
2. bzr branch --use-existing-dir lp:ecryptfs
3. sudo tests/run_one.sh -K -t directory-concurrent.sh -b 1000000 -D /mnt/image 
-l /mnt/lower -u /mnt/upper -f ext2
directory-concurrent    failed to fork child
failed to fork child
...
failed to fork child
failed to fork child
failed to fork child
failed to fork child
failed to fork child
FAIL

Test Summary:
0 passed
1 failed

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: linux-image-4.13.0-22-generic 4.13.0-22.25
ProcVersionSignature: User Name 4.13.0-22.25-generic 4.13.13
Uname: Linux 4.13.0-22-generic x86_64
AlsaDevices:
 total 0
 crw-rw---- 1 root audio 116,  1 Jan  5 08:24 seq
 crw-rw---- 1 root audio 116, 33 Jan  5 08:24 timer
AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
ApportVersion: 2.20.7-0ubuntu3.7
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord'
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
CurrentDmesg:
 [ 5185.596138] EXT4-fs (loop0): mounting ext2 file system using the ext4 
subsystem
 [ 5185.639876] EXT4-fs (loop0): mounted filesystem without journal. Opts: 
user_xattr,acl
Date: Fri Jan  5 09:51:42 2018
IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
MachineType: HP ProLiant DL360 Gen9
PciMultimedia:
 
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=C.UTF-8
 SHELL=/bin/bash
ProcFB: 0 mgadrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-22-generic.efi.signed 
root=UUID=051b34ce-dfed-4e36-aa78-851c5a284ee4 ro
RelatedPackageVersions:
 linux-restricted-modules-4.13.0-22-generic N/A
 linux-backports-modules-4.13.0-22-generic  N/A
 linux-firmware                             1.169.2
RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/27/2015
dmi.bios.vendor: HP
dmi.bios.version: P89
dmi.board.name: ProLiant DL360 Gen9
dmi.board.vendor: HP
dmi.chassis.type: 23
dmi.chassis.vendor: HP
dmi.modalias: 
dmi:bvnHP:bvrP89:bd12/27/2015:svnHP:pnProLiantDL360Gen9:pvr:rvnHP:rnProLiantDL360Gen9:rvr:cvnHP:ct23:cvr:
dmi.product.family: ProLiant
dmi.product.name: ProLiant DL360 Gen9
dmi.sys.vendor: HP

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


** Tags: amd64 apport-bug artful package-from-proposed uec-images

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1741437

Title:
  SRU testing node rumford tend to fail with directory-
  concurrent.sh.ext2 test in ubuntu_ecryptfs test suite

Status in linux package in Ubuntu:
  New

Bug description:
  Reproduce rate 5 out of 5.

  This issue failed frequently on this node, and can be seen on older 4.13 
kernel.
  And this test can pass on the other node. so that this should not be 
considered as a regression in this cycle.
   
  Steps:
  1. Deploy an Artful system
  2. bzr branch --use-existing-dir lp:ecryptfs
  3. sudo tests/run_one.sh -K -t directory-concurrent.sh -b 1000000 -D 
/mnt/image -l /mnt/lower -u /mnt/upper -f ext2
  directory-concurrent  failed to fork child
  failed to fork child
  ...
  failed to fork child
  failed to fork child
  failed to fork child
  failed to fork child
  failed to fork child
  FAIL

  Test Summary:
  0 passed
  1 failed

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-22-generic 4.13.0-22.25
  ProcVersionSignature: User Name 4.13.0-22.25-generic 4.13.13
  Uname: Linux 4.13.0-22-generic x86_64
  AlsaDevices:
   total 0
   crw-rw---- 1 root audio 116,  1 Jan  5 08:24 seq
   crw-rw---- 1 root audio 116, 33 Jan  5 08:24 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDmesg:
   [ 5185.596138] EXT4-fs (loop0): mounting ext2 file system using the ext4 
subsystem
   [ 5185.639876] EXT4-fs (loop0): mounted filesystem without journal. Opts: 
user_xattr,acl
  Date: Fri Jan  5 09:51:42 2018
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  MachineType: HP ProLiant DL360 Gen9
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=<set>
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 mgadrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-22-generic.efi.signed 
root=UUID=051b34ce-dfed-4e36-aa78-851c5a284ee4 ro
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-22-generic N/A
   linux-backports-modules-4.13.0-22-generic  N/A
   linux-firmware                             1.169.2
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/27/2015
  dmi.bios.vendor: HP
  dmi.bios.version: P89
  dmi.board.name: ProLiant DL360 Gen9
  dmi.board.vendor: HP
  dmi.chassis.type: 23
  dmi.chassis.vendor: HP
  dmi.modalias: 
dmi:bvnHP:bvrP89:bd12/27/2015:svnHP:pnProLiantDL360Gen9:pvr:rvnHP:rnProLiantDL360Gen9:rvr:cvnHP:ct23:cvr:
  dmi.product.family: ProLiant
  dmi.product.name: ProLiant DL360 Gen9
  dmi.sys.vendor: HP

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1741437/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to     : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to