This may be unrelated however the failure is also found on disco, 5.0 kernel.  
The actual failure messages themselves are the same, this is on the AWS Cloud, 
across all instance types.  
This relatively new test was added back in Feb.

https://patchwork.ozlabs.org/patch/1048709/


10/01 18:59:01 DEBUG|     utils:0153| [stdout] tag=binfmt_misc01 
stime=1569956330 dur=0 exit=exited stat=0 core=no cu=6 cs=1
10/01 18:59:01 DEBUG|     utils:0153| [stdout] startup='Tue Oct  1 18:58:56 
2019'
10/01 18:59:01 DEBUG|     utils:0153| [stdout] binfmt_misc02 1 TINFO: timeout 
per run is 0h 5m 0s
10/01 18:59:01 DEBUG|     utils:0153| [stdout] binfmt_misc02 1 TFAIL: Recognise 
a disabled binary type successfully
10/01 18:59:01 DEBUG|     utils:0153| [stdout] binfmt_misc02 2 TFAIL: Recognise 
a disabled binary type successfully
10/01 18:59:01 DEBUG|     utils:0153| [stdout] binfmt_misc02 3 TFAIL: Recognise 
a disabled binary type successfully
10/01 18:59:01 DEBUG|     utils:0153| [stdout] binfmt_misc02 4 TFAIL: Recognise 
a disabled binary type successfully
10/01 18:59:01 DEBUG|     utils:0153| [stdout] binfmt_misc02 5 TFAIL: Recognise 
a binary type successfully
10/01 18:59:01 DEBUG|     utils:0153| [stdout] binfmt_misc02 6 TFAIL: Recognise 
a binary type successfully
10/01 18:59:01 DEBUG|     utils:0153| [stdout] binfmt_misc02 7 TINFO: AppArmor 
enabled, this may affect test results
10/01 18:59:01 DEBUG|     utils:0153| [stdout] binfmt_misc02 7 TINFO: it can be 
disabled with TST_DISABLE_APPARMOR=1 (requires super/root)
10/01 18:59:01 DEBUG|     utils:0153| [stdout] binfmt_misc02 7 TINFO: loaded 
AppArmor profiles: modprobe 

** Also affects: linux-aws (Ubuntu)
   Importance: Undecided
       Status: New

** Also affects: linux (Ubuntu Bionic)
   Importance: Undecided
       Status: New

** Also affects: linux-aws (Ubuntu Bionic)
   Importance: Undecided
       Status: New

** Also affects: linux (Ubuntu Disco)
   Importance: Undecided
       Status: New

** Also affects: linux-aws (Ubuntu Disco)
   Importance: Undecided
       Status: New

-- 
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/1822246

Title:
  binfmt_misc02 in LTP kernel/fs/ failed with Bionic

Status in ubuntu-kernel-tests:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in linux-aws package in Ubuntu:
  New
Status in linux source package in Bionic:
  New
Status in linux-aws source package in Bionic:
  New
Status in linux source package in Disco:
  New
Status in linux-aws source package in Disco:
  New

Bug description:
  Found on a KVM node, I think this test case might need some
  investigation, as the LTP suite should be chop down into pieces like
  the syscalls variant.

   <<<test_start>>>
   tag=binfmt_misc02 stime=1553796942
   cmdline="binfmt_misc02.sh"
   contacts=""
   analysis=exit
   <<<test_output>>>
   binfmt_misc02 1 TINFO: timeout per run is 0h 5m 0s
   binfmt_misc02 1 TFAIL: Recognise a disabled binary type successfully
   binfmt_misc02 2 TFAIL: Recognise a disabled binary type successfully
   binfmt_misc02 3 TFAIL: Recognise a disabled binary type successfully
   binfmt_misc02 4 TFAIL: Recognise a disabled binary type successfully
   binfmt_misc02 5 TFAIL: Recognise a binary type successfully
   binfmt_misc02 6 TFAIL: Recognise a binary type successfully
   binfmt_misc02 7 TINFO: AppArmor enabled, this may affect test results
   binfmt_misc02 7 TINFO: You can try to disable it with TST_DISABLE_APPARMOR=1 
(requires super/root)
   binfmt_misc02 7 TINFO: loaded AppArmor profiles: none

   Summary:
   passed   0
   failed   6
   skipped  0
   warnings 0
   <<<execution_status>>>
   initiation_status="ok"
   duration=1 termination_type=exited termination_id=1 corefile=no
   cutime=14 cstime=6
   <<<test_end>>>

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-46-generic 4.15.0-46.49
  ProcVersionSignature: User Name 4.15.0-46.49-generic 4.15.18
  Uname: Linux 4.15.0-46-generic x86_64
  AlsaDevices:
   total 0
   crw-rw---- 1 root audio 116,  1 Mar 29 06:45 seq
   crw-rw---- 1 root audio 116, 33 Mar 29 06:45 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.9-0ubuntu7.6
  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:

  Date: Fri Mar 29 06:48:07 2019
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
  PciMultimedia:

  ProcFB: 0 cirrusdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-46-generic 
root=UUID=2a4b0342-a2dd-4feb-b3e2-9644ca1c4a60 ro
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-46-generic N/A
   linux-backports-modules-4.15.0-46-generic  N/A
   linux-firmware                             1.173.3
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/01/2014
  dmi.bios.vendor: SeaBIOS
  dmi.bios.version: Ubuntu-1.8.2-1ubuntu1
  dmi.chassis.type: 1
  dmi.chassis.vendor: QEMU
  dmi.chassis.version: pc-i440fx-xenial
  dmi.modalias: 
dmi:bvnSeaBIOS:bvrUbuntu-1.8.2-1ubuntu1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-xenial:cvnQEMU:ct1:cvrpc-i440fx-xenial:
  dmi.product.name: Standard PC (i440FX + PIIX, 1996)
  dmi.product.version: pc-i440fx-xenial
  dmi.sys.vendor: QEMU

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1822246/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to     : [email protected]
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to