← Back to team overview

group.of.nepali.translators team mailing list archive

  1. group.of.nepali.translators team
  2. Mailing list archive
  3. Message #47709

[Bug 1887473] Re: timer_settime02 from ubuntu_ltp_syscalls failed on X/B/E/F s390x

  Thread Previous • Date Previous • • Thread Next 
Ubuntu 19.10 (Eoan Ermine) has reached end of life, so this bug will not
be fixed for that specific release.

** Changed in: linux (Ubuntu Eoan)
       Status: Confirmed => Won't Fix

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1887473

Title:
  timer_settime02 from ubuntu_ltp_syscalls failed on X/B/E/F s390x

Status in ubuntu-kernel-tests:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Xenial:
  Confirmed
Status in linux source package in Bionic:
  Confirmed
Status in linux source package in Eoan:
  Won't Fix
Status in linux source package in Focal:
  Confirmed

Bug description:
  Issue found on Xenial 4.4.0-186-generic s390x LPAR / zVM (passed on other arches)
  And B/E/F s390x as well.

  <<<test_start>>>
  tag=timer_settime02 stime=1594698491
  cmdline="timer_settime02"
  contacts=""
  analysis=exit
  <<<test_output>>>
  incrementing stop
  tst_test.c:1247: INFO: Timeout per run is 0h 05m 00s
  timer_settime02.c:78: INFO: Testing variant: syscall with old kernel spec
  timer_settime02.c:89: INFO: Testing for setting new_set pointer to NULL:
  timer_settime02.c:137: PASS: CLOCK_REALTIME failed as expected: EINVAL (22)
  timer_settime02.c:137: PASS: CLOCK_MONOTONIC failed as expected: EINVAL (22)
  timer_settime02.c:143: FAIL: timer_delete() failed!: EINVAL (22)
  timer_settime02.c:137: PASS: CLOCK_PROCESS_CPUTIME_ID failed as expected: EINVAL (22)
  timer_settime02.c:143: FAIL: timer_delete() failed!: EINVAL (22)
  timer_settime02.c:137: PASS: CLOCK_THREAD_CPUTIME_ID failed as expected: EINVAL (22)
  timer_settime02.c:143: FAIL: timer_delete() failed!: EINVAL (22)
  timer_settime02.c:137: PASS: CLOCK_BOOTTIME failed as expected: EINVAL (22)
  timer_settime02.c:143: FAIL: timer_delete() failed!: EINVAL (22)
  timer_settime02.c:106: CONF: CLOCK_BOOTTIME_ALARM unsupported: EOPNOTSUPP (95)
  timer_settime02.c:106: CONF: CLOCK_REALTIME_ALARM unsupported: EOPNOTSUPP (95)
  timer_settime02.c:137: PASS: CLOCK_TAI failed as expected: EINVAL (22)
  timer_settime02.c:143: FAIL: timer_delete() failed!: EINVAL (22)
  timer_settime02.c:89: INFO: Testing for setting tv_nsec to a negative value:
  timer_settime02.c:137: PASS: CLOCK_REALTIME failed as expected: EINVAL (22)
  timer_settime02.c:143: FAIL: timer_delete() failed!: EINVAL (22)
  timer_settime02.c:137: PASS: CLOCK_MONOTONIC failed as expected: EINVAL (22)
  timer_settime02.c:143: FAIL: timer_delete() failed!: EINVAL (22)
  timer_settime02.c:137: PASS: CLOCK_PROCESS_CPUTIME_ID failed as expected: EINVAL (22)
  timer_settime02.c:143: FAIL: timer_delete() failed!: EINVAL (22)
  timer_settime02.c:137: PASS: CLOCK_THREAD_CPUTIME_ID failed as expected: EINVAL (22)
  timer_settime02.c:143: FAIL: timer_delete() failed!: EINVAL (22)
  timer_settime02.c:137: PASS: CLOCK_BOOTTIME failed as expected: EINVAL (22)
  timer_settime02.c:143: FAIL: timer_delete() failed!: EINVAL (22)
  timer_settime02.c:106: CONF: CLOCK_BOOTTIME_ALARM unsupported: EOPNOTSUPP (95)
  timer_settime02.c:106: CONF: CLOCK_REALTIME_ALARM unsupported: EOPNOTSUPP (95)
  timer_settime02.c:137: PASS: CLOCK_TAI failed as expected: EINVAL (22)
  timer_settime02.c:143: FAIL: timer_delete() failed!: EINVAL (22)
  timer_settime02.c:89: INFO: Testing for setting tv_nsec value too high:
  timer_settime02.c:137: PASS: CLOCK_REALTIME failed as expected: EINVAL (22)
  timer_settime02.c:143: FAIL: timer_delete() failed!: EINVAL (22)
  timer_settime02.c:137: PASS: CLOCK_MONOTONIC failed as expected: EINVAL (22)
  timer_settime02.c:143: FAIL: timer_delete() failed!: EINVAL (22)
  timer_settime02.c:137: PASS: CLOCK_PROCESS_CPUTIME_ID failed as expected: EINVAL (22)
  timer_settime02.c:143: FAIL: timer_delete() failed!: EINVAL (22)
  timer_settime02.c:137: PASS: CLOCK_THREAD_CPUTIME_ID failed as expected: EINVAL (22)
  timer_settime02.c:143: FAIL: timer_delete() failed!: EINVAL (22)
  timer_settime02.c:137: PASS: CLOCK_BOOTTIME failed as expected: EINVAL (22)
  timer_settime02.c:143: FAIL: timer_delete() failed!: EINVAL (22)
  timer_settime02.c:106: CONF: CLOCK_BOOTTIME_ALARM unsupported: EOPNOTSUPP (95)
  timer_settime02.c:106: CONF: CLOCK_REALTIME_ALARM unsupported: EOPNOTSUPP (95)
  timer_settime02.c:137: PASS: CLOCK_TAI failed as expected: EINVAL (22)
  timer_settime02.c:143: FAIL: timer_delete() failed!: EINVAL (22)
  timer_settime02.c:89: INFO: Testing for passing pointer to invalid timer_id:
  timer_settime02.c:137: PASS: CLOCK_REALTIME failed as expected: EINVAL (22)
  timer_settime02.c:143: FAIL: timer_delete() failed!: EINVAL (22)
  timer_settime02.c:137: PASS: CLOCK_MONOTONIC failed as expected: EINVAL (22)
  timer_settime02.c:143: FAIL: timer_delete() failed!: EINVAL (22)
  timer_settime02.c:137: PASS: CLOCK_PROCESS_CPUTIME_ID failed as expected: EINVAL (22)
  timer_settime02.c:143: FAIL: timer_delete() failed!: EINVAL (22)
  timer_settime02.c:137: PASS: CLOCK_THREAD_CPUTIME_ID failed as expected: EINVAL (22)
  timer_settime02.c:143: FAIL: timer_delete() failed!: EINVAL (22)
  timer_settime02.c:137: PASS: CLOCK_BOOTTIME failed as expected: EINVAL (22)
  timer_settime02.c:143: FAIL: timer_delete() failed!: EINVAL (22)
  timer_settime02.c:106: CONF: CLOCK_BOOTTIME_ALARM unsupported: EOPNOTSUPP (95)
  timer_settime02.c:106: CONF: CLOCK_REALTIME_ALARM unsupported: EOPNOTSUPP (95)
  timer_settime02.c:137: PASS: CLOCK_TAI failed as expected: EINVAL (22)
  timer_settime02.c:143: FAIL: timer_delete() failed!: EINVAL (22)
  timer_settime02.c:89: INFO: Testing for passing invalid address for new_value:
  timer_settime02.c:137: PASS: CLOCK_REALTIME failed as expected: EFAULT (14)
  timer_settime02.c:143: FAIL: timer_delete() failed!: EINVAL (22)
  timer_settime02.c:137: PASS: CLOCK_MONOTONIC failed as expected: EFAULT (14)
  timer_settime02.c:143: FAIL: timer_delete() failed!: EINVAL (22)
  timer_settime02.c:137: PASS: CLOCK_PROCESS_CPUTIME_ID failed as expected: EFAULT (14)
  timer_settime02.c:143: FAIL: timer_delete() failed!: EINVAL (22)
  timer_settime02.c:137: PASS: CLOCK_THREAD_CPUTIME_ID failed as expected: EFAULT (14)
  timer_settime02.c:143: FAIL: timer_delete() failed!: EINVAL (22)
  timer_settime02.c:137: PASS: CLOCK_BOOTTIME failed as expected: EFAULT (14)
  timer_settime02.c:143: FAIL: timer_delete() failed!: EINVAL (22)
  timer_settime02.c:106: CONF: CLOCK_BOOTTIME_ALARM unsupported: EOPNOTSUPP (95)
  timer_settime02.c:106: CONF: CLOCK_REALTIME_ALARM unsupported: EOPNOTSUPP (95)
  timer_settime02.c:137: PASS: CLOCK_TAI failed as expected: EFAULT (14)
  timer_settime02.c:143: FAIL: timer_delete() failed!: EINVAL (22)
  timer_settime02.c:89: INFO: Testing for passing invalid address for old_value:
  timer_settime02.c:133: FAIL: CLOCK_REALTIME didn't fail as expected. Expected: EFAULT - Got: EINVAL (22)
  timer_settime02.c:143: FAIL: timer_delete() failed!: EINVAL (22)
  timer_settime02.c:133: FAIL: CLOCK_MONOTONIC didn't fail as expected. Expected: EFAULT - Got: EINVAL (22)
  timer_settime02.c:143: FAIL: timer_delete() failed!: EINVAL (22)
  timer_settime02.c:133: FAIL: CLOCK_PROCESS_CPUTIME_ID didn't fail as expected. Expected: EFAULT - Got: EINVAL (22)
  timer_settime02.c:143: FAIL: timer_delete() failed!: EINVAL (22)
  timer_settime02.c:133: FAIL: CLOCK_THREAD_CPUTIME_ID didn't fail as expected. Expected: EFAULT - Got: EINVAL (22)
  timer_settime02.c:143: FAIL: timer_delete() failed!: EINVAL (22)
  timer_settime02.c:133: FAIL: CLOCK_BOOTTIME didn't fail as expected. Expected: EFAULT - Got: EINVAL (22)
  timer_settime02.c:143: FAIL: timer_delete() failed!: EINVAL (22)
  timer_settime02.c:106: CONF: CLOCK_BOOTTIME_ALARM unsupported: EOPNOTSUPP (95)
  timer_settime02.c:106: CONF: CLOCK_REALTIME_ALARM unsupported: EOPNOTSUPP (95)
  timer_settime02.c:133: FAIL: CLOCK_TAI didn't fail as expected. Expected: EFAULT - Got: EINVAL (22)
  timer_settime02.c:143: FAIL: timer_delete() failed!: EINVAL (22)

  HINT: You _MAY_ be missing kernel fixes, see:

  https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=f18ddc13af98

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

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-186-generic 4.4.0-186.216
  ProcVersionSignature: Ubuntu 4.4.0-186.216-generic 4.4.228
  Uname: Linux 4.4.0-186-generic s390x
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access '/dev/snd/': No such file or directory
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.1-0ubuntu2.23
  Architecture: s390x
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found.
  Date: Mon Jul 13 23:42:15 2020
  HibernationDevice: RESUME=UUID=f578fa27-1d57-41c9-bb1d-7ff64c1c9345
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=<set>
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: Error: [Errno 2] No such file or directory: '/proc/fb'
  ProcKernelCmdLine: root=UUID=f26894a2-496d-4891-aa9a-f66344c77779 crashkernel=196M BOOT_IMAGE=0
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-186-generic N/A
   linux-backports-modules-4.4.0-186-generic  N/A
   linux-firmware                             1.157.23
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)

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

References

  Thread Previous • Date Previous • • Thread Next