[Canonical-ubuntu-qa] [Bug 2078315] Re: creat07, execve04, ioctl_loop02, ioctl_loop06, ioctl_loop07 from ubuntu_ltp_syscalls failed on N-OEM-6.11
** Changed in: ubuntu-kernel-tests Status: New => In Progress ** Changed in: ubuntu-kernel-tests Assignee: (unassigned) => Po-Hsu Lin (cypressyew) -- You received this bug notification because you are a member of Canonical Platform QA Team, which is subscribed to ubuntu-kernel-tests. https://bugs.launchpad.net/bugs/2078315 Title: creat07, execve04, ioctl_loop02, ioctl_loop06, ioctl_loop07 from ubuntu_ltp_syscalls failed on N-OEM-6.11 Status in ubuntu-kernel-tests: In Progress Bug description: Issue found on 6.11.0-1001.1 Investigation shows that we will need to update our LTP fork to the following commits: * creat07, execve04 - 12588eee syscalls/execve04,creat07: skip for kernels 6.11 and later * ioctl_loop02, ioctl_loop06, ioctl_loop07 - c02d8ddc lib: make tst_detach_device_by_fd() also close dev_fd Test output: COMMAND:/opt/ltp-upstream/bin/ltp-pan -e -S -a 147118 -n 147118 -p -f /tmp/ltp-qq6AS8PjLk/alltests -l /opt/ltp-upstream/results/LTP_RUN_ON-2024_08_29-07h_19m_37s.log -C /opt/ltp-upstream/output/LTP_RUN_ON-2024_08_29-07h_19m_37s.failed -T /opt/ltp-upstream/output/LTP_RUN_ON-2024_08_29-07h_19m_37s.tconf LOG File: /opt/ltp-upstream/results/LTP_RUN_ON-2024_08_29-07h_19m_37s.log FAILED COMMAND File: /opt/ltp-upstream/output/LTP_RUN_ON-2024_08_29-07h_19m_37s.failed TCONF COMMAND File: /opt/ltp-upstream/output/LTP_RUN_ON-2024_08_29-07h_19m_37s.tconf Running tests... <<>> tag=creat07 stime=1724915977 cmdline="creat07" contacts="" analysis=exit <<>> tst_test.c:1806: TINFO: LTP version: 20240524-101-gc5d95b6d3 tst_test.c:1650: TINFO: Timeout per run is 0h 00m 30s creat07.c:37: TFAIL: creat() succeeded unexpectedly Test timeouted, sending SIGKILL! tst_test.c:1698: TINFO: Killed the leftover descendant processes tst_test.c:1704: TINFO: If you are running on slow machine, try exporting LTP_TIMEOUT_MUL > 1 tst_test.c:1706: TBROK: Test killed! (timeout?) Summary: passed 0 failed 1 broken 1 skipped 0 warnings 0 <<>> initiation_status="ok" duration=30 termination_type=exited termination_id=3 corefile=no cutime=0 cstime=0 <<>> <<>> tag=execve04 stime=1724916007 cmdline="execve04" contacts="" analysis=exit <<>> tst_test.c:1806: TINFO: LTP version: 20240524-101-gc5d95b6d3 tst_test.c:1650: TINFO: Timeout per run is 0h 00m 30s execve_child.c:27: TFAIL: execve_child shouldn't be executed tst_test.c:1698: TINFO: Killed the leftover descendant processes Summary: passed 0 failed 1 broken 0 skipped 0 warnings 0 <<>> initiation_status="ok" duration=0 termination_type=exited termination_id=1 corefile=no cutime=0 cstime=1 <<>> <<>> tag=ioctl_loop02 stime=1724916007 cmdline="ioctl_loop02" contacts="" analysis=exit <<>> tst_test.c:1806: TINFO: LTP version: 20240524-101-gc5d95b6d3 tst_test.c:1650: TINFO: Timeout per run is 0h 00m 30s tst_device.c:96: TINFO: Found free device 0 '/dev/loop0' tst_buffers.c:57: TINFO: Test is using guarded buffers ioctl_loop02.c:56: TINFO: Using LOOP_SET_FD to setup loopdevice ioctl_loop02.c:67: TPASS: /sys/block/loop0/ro = 1 ioctl_loop02.c:68: TPASS: /sys/block/loop0/loop/backing_file = '/tmp/ltp-qq6AS8PjLk/LTP_iocWAhE0P/test.img' ioctl_loop02.c:77: TPASS: lo_flags only has default LO_FLAGS_READ_ONLY flag ioctl_loop02.c:83: TPASS: Can not write data in RO mode: EPERM (1) ioctl_loop02.c:89: TPASS: LOOP_CHANGE_FD succeeded ioctl_loop02.c:90: TPASS: /sys/block/loop0/ro = 1 ioctl_loop02.c:91: TPASS: /sys/block/loop0/loop/backing_file = '/tmp/ltp-qq6AS8PjLk/LTP_iocWAhE0P/test1.img' ioctl_loop02.c:97: TPASS: LOOP_CHANGE_FD failed as expected: EINVAL (22) ioctl_loop02.c:56: TINFO: Using LOOP_CONFIGURE with read_only flag ioctl_loop02.c:63: TBROK: ioctl(5,(0x4C0A),...) failed: EBUSY (16) Summary: passed 8 failed 0 broken 1 skipped 0 warnings 0 <<>> initiation_status="ok" duration=0 termination_type=exited termination_id=2 corefile=no cutime=0 cstime=0 <<>> <<>> tag=ioctl_loop06 stime=1724916007 cmdline="ioctl_loop06" contacts="" analysis=exit <<>> tst_test.c:1806: TINFO: LTP version: 20240524-101-gc5d95b6d3 tst_test.c:1650: TINFO: Timeout per run is 0h 00m 30s tst_device.c:96: TINFO: Found free device 0 '/dev/loop0' ioctl_loop06.c:74: TINFO: Using LOOP_SET_BLOCK_SIZE with arg < 512 ioctl_loop06.c:65: TPASS: Set block size failed as expected: EINVAL (22) ioctl_loop06.c:74: TINFO: Using LOOP_SET_BLOCK_SIZE with arg > PAGE_SIZE ioctl_loop06.c:65: TPASS: Set block size failed as expected: EINVAL (22) ioctl_loop06.c:74: TINFO: Using LOOP_SET_BLOCK_SIZE with arg != power_of_2 ioctl_loop06.c:65: TPASS: Set block size failed as expected: EINVAL (22) ioctl_loop06.c:74: TINFO: Using LOOP_CONFIGURE with block_size < 512 ioctl_loop06.c:67: TFAIL: Set block size failed expected EINVAL got: EBUSY (16) ioctl_loop06.c:74: TINFO
[Canonical-ubuntu-qa] [Bug 1939118] Re: vmx_db_test in vmx from ubuntu_kvm_unit_tests failed on B-4.15 amd64
Test result with O-azure-6.11-1003 (6 failures reported): Test suite: vmx_db_test Hardware delivered single-step PASS: Expected #DB VM-exit PASS: Expected RIP 0x406085 (actual 406085) PASS: Expected pending debug exceptions 0 (actual 0) PASS: Expected exit qualification 4000 (actual 4000) PASS: Expected DR6 4ffa (actual 4ffa) Hardware delivered single-step in MOVSS shadow PASS: Expected #DB VM-exit PASS: Expected RIP 0x406089 (actual 406089) PASS: Expected pending debug exceptions 0 (actual 0) PASS: Expected exit qualification 4001 (actual 4001) PASS: Expected DR6 4ffa (actual 4ffa) Software synthesized single-step FAIL: Expected #DB VM-exit PASS: Expected RIP 0x40608e (actual 40608e) PASS: Expected pending debug exceptions 0 (actual 0) FAIL: Expected exit qualification 4000 (actual 0) PASS: Expected DR6 4ffa (actual 4ffa) Software synthesized single-step in MOVSS shadow PASS: Expected #DB VM-exit PASS: Expected RIP 0x406093 (actual 406093) XPASS: Expected pending debug exceptions 0 (actual 0) XPASS: Expected exit qualification 4001 (actual 4001) PASS: Expected DR6 4ffa (actual 4ffa) Hardware delivered single-step in transactional region PASS: Expected #DB VM-exit FAIL: Expected RIP 0x406096 (actual 4014db) PASS: Expected pending debug exceptions 0 (actual 0) FAIL: Expected exit qualification 1 (actual 4000) PASS: Expected DR6 4ffa (actual 4ffa) filter = vmx_db_test, test = vmx_nmi_window_test ... filter = vmx_db_test, test = vmx_exception_test SUMMARY: 53 tests, 6 unexpected failures FAIL vmx_db_test (53 tests, 6 unexpected failures) -- You received this bug notification because you are a member of Canonical Platform QA Team, which is subscribed to ubuntu-kernel-tests. https://bugs.launchpad.net/bugs/1939118 Title: vmx_db_test in vmx from ubuntu_kvm_unit_tests failed on B-4.15 amd64 Status in ubuntu-kernel-tests: New Bug description: Issue found on node glameow with 4.15.0-153 The vmx test can proceed with vmx_hlt_with_rvi_test (bug 1822308) move out as a standalone test. Test suite: vmx_db_test Hardware delivered single-step PASS: Expected #DB VM-exit PASS: Expected RIP 0x4043d8 (actual 4043d8) PASS: Expected pending debug exceptions 0 (actual 0) PASS: Expected exit qualification 4000 (actual 4000) PASS: Expected DR6 2ffa (actual 2ffa) Hardware delivered single-step in MOVSS shadow PASS: Expected #DB VM-exit PASS: Expected RIP 0x4043dc (actual 4043dc) PASS: Expected pending debug exceptions 0 (actual 0) PASS: Expected exit qualification 4001 (actual 4001) PASS: Expected DR6 2ffa (actual 2ffa) Software synthesized single-step PASS: Expected #DB VM-exit PASS: Expected RIP 0x4043e1 (actual 4043e1) PASS: Expected pending debug exceptions 0 (actual 0) FAIL: Expected exit qualification 4000 (actual 6000) FAIL: Expected DR6 2ffa (actual 6ff0) Software synthesized single-step in MOVSS shadow PASS: Expected #DB VM-exit PASS: Expected RIP 0x4043e6 (actual 4043e6) XFAIL: Expected pending debug exceptions 0 (actual 5001) XFAIL: Expected exit qualification 4001 (actual 6000) FAIL: Expected DR6 2ffa (actual 6ff0) filter = -exit_monitor_from_l2_test, test = vmx_nmi_window_test filter = -exit_monitor_from_l2_test, test = vmx_intr_window_test filter = -exit_monitor_from_l2_test, test = vmx_pending_event_test filter = -exit_monitor_from_l2_test, test = vmx_pending_event_hlt_test To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1939118/+subscriptions -- Mailing list: https://launchpad.net/~canonical-ubuntu-qa Post to : canonical-ubuntu-qa@lists.launchpad.net Unsubscribe : https://launchpad.net/~canonical-ubuntu-qa More help : https://help.launchpad.net/ListHelp
[Canonical-ubuntu-qa] [Bug 2076381] Re: [MIR] retry
Override component to main retry 1.0.4-3build1 in jammy: universe/misc -> main retry 1.0.4-3build1 in jammy amd64: universe/utils/optional/30% -> main retry 1.0.4-3build1 in jammy arm64: universe/utils/optional/30% -> main retry 1.0.4-3build1 in jammy armhf: universe/utils/optional/30% -> main retry 1.0.4-3build1 in jammy ppc64el: universe/utils/optional/30% -> main retry 1.0.4-3build1 in jammy riscv64: universe/utils/optional/30% -> main retry 1.0.4-3build1 in jammy s390x: universe/utils/optional/30% -> main Override [y|N]? y 7 publications overridden. ** Changed in: retry (Ubuntu Jammy) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Canonical's Ubuntu QA, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/2076381 Title: [MIR] retry Status in retry package in Ubuntu: Fix Released Status in retry source package in Jammy: Fix Released Status in retry source package in Noble: In Progress Status in retry source package in Oracular: Fix Released Bug description: [Availability] The package `retry` is already in Ubuntu universe. The package `retry` build for the architectures it is designed to work on. It currently builds and works for architectures: any Link to package https://launchpad.net/ubuntu/+source/retry [Rationale] This package is required in ubuntu/main as it is a dependency for `autopkgtest`, which is already in main (https://launchpad.net/ubuntu/+source/autopkgtest). Also, this package only consist of a single binary produced from less than 700 lines of quite clear modern C, including error handling and built-in usage (--help). It basically eases creating retry loop in scripts, with non trivial features such as variable delay between retries, and stdout/stderr handling. [Security] - No CVEs/security issues in this software in the past - no `suid` or `sgid` binaries - no executables in `/sbin` and `/usr/sbin` - Package does not install services, timers or recurring jobs - Packages does not open privileged ports (ports < 1024). - Package does not expose any external endpoints - Packages does not contain extensions to security-sensitive software [Quality assurance - function/usage] - The package works well right after install [Quality assurance - maintenance] - The package is maintained well in Debian/Ubuntu/Upstream and does not have too many, long-term & critical, open bugs - Ubuntu https://bugs.launchpad.net/ubuntu/+source/retry/+bug - Debian https://bugs.debian.org/cgi-bin/pkgreport.cgi?src=retry - Upstream's bug tracker, e.g., GitHub Issues: https://github.com/minfrin/retry/issues - The package does not deal with exotic hardware we cannot support [Quality assurance - testing] - The package does not run a test at build time because there is no test suite in the upstream repository. - The package runs a non-trivial autopkgtest, and is currently passing on all architectures, link to test logs: https://autopkgtest.ubuntu.com/packages/retry - The package does have not failing autopkgtests right now [Quality assurance - packaging] - debian/watch is present and works - debian/control defines a correct Maintainer field - This package does not yield massive lintian Warnings, Errors - https://buildd.debian.org/status/fetch.php?pkg=retry&arch=arm64&ver=1.0.5-3&stamp=1674427627&raw=1 - `lintian --pedantic` doesn't yield anything - This package does not rely on obsolete or about to be demoted packages. - The package will not be installed by default - Packaging and build is easy, link to debian/rules: https://git.launchpad.net/ubuntu/+source/retry/tree/debian/rules?h=applied/1.0.5-3&id=30ac5a739df4896a8094615af83ecb9962806f9e [UI standards] - Application is not end-user facing (does not need translation) [Dependencies] - No further depends or recommends dependencies that are not yet in main [Standards compliance] - This package correctly follows FHS and Debian Policy [Maintenance/Owner] - I suggest the owning team to be Foundations, more specifically Ubuntu Release Management Team, and as part of that team, I certify that we agree to maintain the package - This does not use static builds - This does not use vendored code - This package is not rust based - The package has been built within the last 3 months in PPA - Build link on launchpad: https://launchpad.net/~hyask/+archive/ubuntu/tests/+build/28725690 [Background information] The Package description explains the package well. Upstream Name is `retry` Link to upstream project: https://github.com/minfrin/retry To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/retry/+bug/2076381/+subscriptions -- Mailing list: https://launchpad.net/~canonical-ubuntu-qa Post to : canonical-ubuntu-qa@lists.launchpad.net Unsubscribe : https://launchpad.net/~canonical-ubuntu-qa More help
[Canonical-ubuntu-qa] [Bug 2076381] Re: [MIR] retry
Override component to main retry 1.0.5-3build1~ubuntu0.24.04.1 in noble: universe/misc -> main retry 1.0.5-3build1~ubuntu0.24.04.1 in noble amd64: universe/utils/optional/40% -> main retry 1.0.5-3build1~ubuntu0.24.04.1 in noble arm64: universe/utils/optional/40% -> main retry 1.0.5-3build1~ubuntu0.24.04.1 in noble armhf: universe/utils/optional/40% -> main retry 1.0.5-3build1~ubuntu0.24.04.1 in noble ppc64el: universe/utils/optional/40% -> main retry 1.0.5-3build1~ubuntu0.24.04.1 in noble riscv64: universe/utils/optional/40% -> main retry 1.0.5-3build1~ubuntu0.24.04.1 in noble s390x: universe/utils/optional/40% -> main Override [y|N]? y 7 publications overridden. ** Changed in: retry (Ubuntu Noble) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Canonical's Ubuntu QA, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/2076381 Title: [MIR] retry Status in retry package in Ubuntu: Fix Released Status in retry source package in Jammy: Fix Released Status in retry source package in Noble: Fix Released Status in retry source package in Oracular: Fix Released Bug description: [Availability] The package `retry` is already in Ubuntu universe. The package `retry` build for the architectures it is designed to work on. It currently builds and works for architectures: any Link to package https://launchpad.net/ubuntu/+source/retry [Rationale] This package is required in ubuntu/main as it is a dependency for `autopkgtest`, which is already in main (https://launchpad.net/ubuntu/+source/autopkgtest). Also, this package only consist of a single binary produced from less than 700 lines of quite clear modern C, including error handling and built-in usage (--help). It basically eases creating retry loop in scripts, with non trivial features such as variable delay between retries, and stdout/stderr handling. [Security] - No CVEs/security issues in this software in the past - no `suid` or `sgid` binaries - no executables in `/sbin` and `/usr/sbin` - Package does not install services, timers or recurring jobs - Packages does not open privileged ports (ports < 1024). - Package does not expose any external endpoints - Packages does not contain extensions to security-sensitive software [Quality assurance - function/usage] - The package works well right after install [Quality assurance - maintenance] - The package is maintained well in Debian/Ubuntu/Upstream and does not have too many, long-term & critical, open bugs - Ubuntu https://bugs.launchpad.net/ubuntu/+source/retry/+bug - Debian https://bugs.debian.org/cgi-bin/pkgreport.cgi?src=retry - Upstream's bug tracker, e.g., GitHub Issues: https://github.com/minfrin/retry/issues - The package does not deal with exotic hardware we cannot support [Quality assurance - testing] - The package does not run a test at build time because there is no test suite in the upstream repository. - The package runs a non-trivial autopkgtest, and is currently passing on all architectures, link to test logs: https://autopkgtest.ubuntu.com/packages/retry - The package does have not failing autopkgtests right now [Quality assurance - packaging] - debian/watch is present and works - debian/control defines a correct Maintainer field - This package does not yield massive lintian Warnings, Errors - https://buildd.debian.org/status/fetch.php?pkg=retry&arch=arm64&ver=1.0.5-3&stamp=1674427627&raw=1 - `lintian --pedantic` doesn't yield anything - This package does not rely on obsolete or about to be demoted packages. - The package will not be installed by default - Packaging and build is easy, link to debian/rules: https://git.launchpad.net/ubuntu/+source/retry/tree/debian/rules?h=applied/1.0.5-3&id=30ac5a739df4896a8094615af83ecb9962806f9e [UI standards] - Application is not end-user facing (does not need translation) [Dependencies] - No further depends or recommends dependencies that are not yet in main [Standards compliance] - This package correctly follows FHS and Debian Policy [Maintenance/Owner] - I suggest the owning team to be Foundations, more specifically Ubuntu Release Management Team, and as part of that team, I certify that we agree to maintain the package - This does not use static builds - This does not use vendored code - This package is not rust based - The package has been built within the last 3 months in PPA - Build link on launchpad: https://launchpad.net/~hyask/+archive/ubuntu/tests/+build/28725690 [Background information] The Package description explains the package well. Upstream Name is `retry` Link to upstream project: https://github.com/minfrin/retry To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/retry/+bug/2076381/+subscriptions -- Mailing list: https://launchpad.net/~canonical-ubuntu-qa Post
