Failed on D-AWS (t3.medium), this failure was not spotted across all instances
Test failed with vfat.: tst_mkfs.c:90: INFO: Formatting /dev/loop3 with vfat opts='' extra opts='' sync_file_range02.c:111: INFO: Pre-filling file sync_file_range02.c:71: PASS: Sync equals write sync_file_range02.c:74: FAIL: Sync inside of write: Synced 27854336, expected 16777216 sync_file_range02.c:71: PASS: Sync overlaps with write -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1819116 Title: sync_file_range02 in ubuntu_ltp_syscalls fails Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Incomplete Status in linux-aws package in Ubuntu: New Status in linux-azure package in Ubuntu: New Status in linux-gke package in Ubuntu: New Status in linux source package in Bionic: New Status in linux-aws source package in Bionic: New Status in linux-azure source package in Bionic: New Status in linux-gke source package in Bionic: New Status in linux source package in Cosmic: New Status in linux-aws source package in Cosmic: New Status in linux-azure source package in Cosmic: New Status in linux source package in Disco: Incomplete Status in linux-aws source package in Disco: New Status in linux-azure source package in Disco: New Status in linux source package in Eoan: Incomplete Status in linux-aws source package in Eoan: New Status in linux-azure source package in Eoan: New Status in linux-gke source package in Eoan: New Bug description: syslog output attached as attachment. <<<test_output>>> incrementing stop tst_device.c:231: INFO: Using test device LTP_DEV='/dev/loop2' tst_supported_fs_types.c:72: INFO: Kernel supports ext2 tst_supported_fs_types.c:56: INFO: mkfs.ext2 does exist tst_supported_fs_types.c:72: INFO: Kernel supports ext3 tst_supported_fs_types.c:56: INFO: mkfs.ext3 does exist tst_supported_fs_types.c:72: INFO: Kernel supports ext4 tst_supported_fs_types.c:56: INFO: mkfs.ext4 does exist tst_supported_fs_types.c:72: INFO: Kernel supports xfs tst_supported_fs_types.c:56: INFO: mkfs.xfs does exist tst_supported_fs_types.c:72: INFO: Kernel supports btrfs tst_supported_fs_types.c:56: INFO: mkfs.btrfs does exist tst_supported_fs_types.c:72: INFO: Kernel supports vfat tst_supported_fs_types.c:56: INFO: mkfs.vfat does exist tst_supported_fs_types.c:95: INFO: Filesystem exfat is not supported tst_supported_fs_types.c:72: INFO: Kernel supports ntfs tst_supported_fs_types.c:56: INFO: mkfs.ntfs does exist tst_test.c:1157: INFO: Testing on ext2 tst_mkfs.c:90: INFO: Formatting /dev/loop2 with ext2 opts='' extra opts='' mke2fs 1.44.6 (5-Mar-2019) tst_test.c:1096: INFO: Timeout per run is 0h 05m 00s sync_file_range02.c:54: PASS: Test file range synced to device tst_test.c:1157: INFO: Testing on ext3 tst_mkfs.c:90: INFO: Formatting /dev/loop2 with ext3 opts='' extra opts='' mke2fs 1.44.6 (5-Mar-2019) tst_test.c:1096: INFO: Timeout per run is 0h 05m 00s sync_file_range02.c:54: PASS: Test file range synced to device tst_test.c:1157: INFO: Testing on ext4 tst_mkfs.c:90: INFO: Formatting /dev/loop2 with ext4 opts='' extra opts='' mke2fs 1.44.6 (5-Mar-2019) tst_test.c:1096: INFO: Timeout per run is 0h 05m 00s sync_file_range02.c:54: PASS: Test file range synced to device tst_test.c:1157: INFO: Testing on xfs tst_mkfs.c:90: INFO: Formatting /dev/loop2 with xfs opts='' extra opts='' tst_test.c:1096: INFO: Timeout per run is 0h 05m 00s sync_file_range02.c:54: PASS: Test file range synced to device tst_test.c:1157: INFO: Testing on btrfs tst_mkfs.c:90: INFO: Formatting /dev/loop2 with btrfs opts='' extra opts='' tst_test.c:1096: INFO: Timeout per run is 0h 05m 00s sync_file_range02.c:54: PASS: Test file range synced to device tst_test.c:1157: INFO: Testing on vfat tst_mkfs.c:90: INFO: Formatting /dev/loop2 with vfat opts='' extra opts='' tst_test.c:1096: INFO: Timeout per run is 0h 05m 00s sync_file_range02.c:54: PASS: Test file range synced to device tst_test.c:1157: INFO: Testing on ntfs tst_mkfs.c:90: INFO: Formatting /dev/loop2 with ntfs opts='' extra opts='' The partition start sector was not specified for /dev/loop2 and it could not be obtained automatically. It has been set to 0. The number of sectors per track was not specified for /dev/loop2 and it could not be obtained automatically. It has been set to 0. The number of heads was not specified for /dev/loop2 and it could not be obtained automatically. It has been set to 0. To boot from a device, Windows needs the 'partition start sector', the 'sectors per track' and the 'number of heads' to be set. Windows will not be able to boot from this device. safe_macros.c:739: INFO: Trying FUSE... tst_test.c:1096: INFO: Timeout per run is 0h 05m 00s sync_file_range02.c:56: FAIL: Synced 0, expected 33554432 Summary: passed 6 failed 1 skipped 0 warnings 0 <<<execution_status>>> initiation_status="ok" duration=11 termination_type=exited termination_id=1 corefile=no cutime=10 cstime=157 <<<test_end>>> INFO: ltp-pan reported some tests FAIL LTP Version: 20190115 ############################################################### Done executing testcases. LTP Version: 20190115 ############################################################### ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: linux-image-5.0.0-7-generic 5.0.0-7.8 ProcVersionSignature: User Name 5.0.0-7.8-generic 5.0.0 Uname: Linux 5.0.0-7-generic x86_64 AlsaDevices: total 0 crw-rw---- 1 root audio 116, 1 Mar 8 06:01 seq crw-rw---- 1 root audio 116, 33 Mar 8 06:01 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.10-0ubuntu23 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 8 07:02:13 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-5.0.0-7-generic root=UUID=2a4b0342-a2dd-4feb-b3e2-9644ca1c4a60 ro console=ttyS0,1152008n1 RelatedPackageVersions: linux-restricted-modules-5.0.0-7-generic N/A linux-backports-modules-5.0.0-7-generic N/A linux-firmware 1.177 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/1819116/+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
