[Canonical-ubuntu-qa] [Bug 1862904] Re: cpuset_memory from controller in LTP failed with Eoan
Eoan EOL and we didn't have this hint in our database. ** Changed in: ubuntu-kernel-tests Status: New => Invalid -- 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/1862904 Title: cpuset_memory from controller in LTP failed with Eoan Status in ubuntu-kernel-tests: Invalid Bug description: Issue found on P9 node "baltar". this is a new issue after bug 1836188 was fixed locally. startup='Thu Feb 6 03:47:48 2020' cpuset_memory 1 TPASS: Cpuset memory allocation test succeeded. cpuset_memory 3 TPASS: Cpuset memory allocation test succeeded. cpuset_memory 5 TPASS: Cpuset memory allocation test succeeded. cpuset_memory 7 TPASS: Cpuset memory allocation test succeeded. cpuset_memory 9 TPASS: Cpuset memory allocation test succeeded. cpuset_memory 11 TPASS: Cpuset memory allocation test succeeded. cpuset_memory 13 TPASS: Cpuset memory allocation test succeeded. cpuset_memory 15 TPASS: Cpuset memory allocation test succeeded. cpuset_memory 17 TINFO: /bin/echo: write error: Invalid argument cpuset_memory 17 TFAIL: set general group parameter failed. cpuset_memory 19 TINFO: /bin/echo: write error: Invalid argument cpuset_memory 19 TFAIL: set general group2's parameter failed. cpuset_memory 21 TINFO: /bin/echo: write error: Invalid argument cpuset_memory 21 TFAIL: set general group2's parameter failed. cpuset_memory 23 TINFO: /bin/echo: write error: Invalid argument cpuset_memory 23 TFAIL: set general group's parameter failed. cpuset_memory 25 TINFO: /bin/echo: write error: Invalid argument cpuset_memory 25 TFAIL: set general group's parameter failed. cpuset_memory 27 TINFO: /bin/echo: write error: Invalid argument cpuset_memory 27 TFAIL: set general group2's parameter failed. cpuset_memory 29 TINFO: /bin/echo: write error: Invalid argument cpuset_memory 29 TFAIL: set general group2's parameter failed. cpuset_memory 31 TINFO: /bin/echo: write error: Invalid argument cpuset_memory 31 TFAIL: set general group2's parameter failed. cpuset_memory 33 TINFO: /bin/echo: write error: Invalid argument cpuset_memory 33 TFAIL: set general group1's parameter failed. cpuset_memory 35 TINFO: /bin/echo: write error: Invalid argument cpuset_memory 35 TFAIL: set general group1's parameter failed. tag=cpuset_memory stime=1580960868 dur=24 exit=exited stat=1 core=no cu=27 cs=22 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1862904/+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 2047694] [NEW] mm:cpuset01 from ubuntu_ltp flaky on scobee-kernel with J-realtime
Public bug reported: It seems we didn't run this test on scobee-kernel with J-realtime before, so it's a bit difficult to determine if this is caused by the recent LTP fork update [1]. Test failed with timeout: INFO: Test start time: Thu Dec 21 09:12:45 UTC 2023 COMMAND:/opt/ltp/bin/ltp-pan -q -e -S -a 244473 -n 244473 -f /tmp/ltp-SeaoDkJ1R1/alltests -l /dev/null -C /dev/null -T /dev/null LOG File: /dev/null FAILED COMMAND File: /dev/null TCONF COMMAND File: /dev/null Running tests... tst_test.c:1690: TINFO: LTP version: 20230929-185-g19ef6521d tst_test.c:1574: TINFO: Timeout per run is 0h 00m 30s Test timeouted, sending SIGKILL! tst_test.c:1622: TINFO: Killed the leftover descendant processes tst_test.c:1628: TINFO: If you are running on slow machine, try exporting LTP_TIMEOUT_MUL > 1 tst_test.c:1630: TBROK: Test killed! (timeout?) Summary: passed 0 failed 0 broken 1 skipped 0 warnings 0 INFO: ltp-pan reported some tests FAIL LTP Version: 20230929-185-g19ef6521d INFO: Test end time: Thu Dec 21 09:13:15 UTC 2023 I tried to test this manually on scobee-kernel, but I found this is a bit flaky. In some attempts this test can finish with 10 seconds, but sometimes it will take up to 90 seconds. Maybe bumping the timeout multiplier can be a possible solution. [1] https://lists.ubuntu.com/archives/kernel- team/2023-December/147590.html ** Affects: ubuntu-kernel-tests Importance: Undecided Status: New ** Tags: 5.15 arm64 jammy realtime ubuntu-ltp -- 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/2047694 Title: mm:cpuset01 from ubuntu_ltp flaky on scobee-kernel with J-realtime Status in ubuntu-kernel-tests: New Bug description: It seems we didn't run this test on scobee-kernel with J-realtime before, so it's a bit difficult to determine if this is caused by the recent LTP fork update [1]. Test failed with timeout: INFO: Test start time: Thu Dec 21 09:12:45 UTC 2023 COMMAND:/opt/ltp/bin/ltp-pan -q -e -S -a 244473 -n 244473 -f /tmp/ltp-SeaoDkJ1R1/alltests -l /dev/null -C /dev/null -T /dev/null LOG File: /dev/null FAILED COMMAND File: /dev/null TCONF COMMAND File: /dev/null Running tests... tst_test.c:1690: TINFO: LTP version: 20230929-185-g19ef6521d tst_test.c:1574: TINFO: Timeout per run is 0h 00m 30s Test timeouted, sending SIGKILL! tst_test.c:1622: TINFO: Killed the leftover descendant processes tst_test.c:1628: TINFO: If you are running on slow machine, try exporting LTP_TIMEOUT_MUL > 1 tst_test.c:1630: TBROK: Test killed! (timeout?) Summary: passed 0 failed 0 broken 1 skipped 0 warnings 0 INFO: ltp-pan reported some tests FAIL LTP Version: 20230929-185-g19ef6521d INFO: Test end time: Thu Dec 21 09:13:15 UTC 2023 I tried to test this manually on scobee-kernel, but I found this is a bit flaky. In some attempts this test can finish with 10 seconds, but sometimes it will take up to 90 seconds. Maybe bumping the timeout multiplier can be a possible solution. [1] https://lists.ubuntu.com/archives/kernel- team/2023-December/147590.html To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/2047694/+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 2047694] Re: mm:cpuset01 from ubuntu_ltp flaky on scobee-kernel with J-realtime
** Description changed: It seems we didn't run this test on scobee-kernel with J-realtime before, so it's a bit difficult to determine if this is caused by the recent LTP fork update [1]. Test failed with timeout: INFO: Test start time: Thu Dec 21 09:12:45 UTC 2023 COMMAND:/opt/ltp/bin/ltp-pan -q -e -S -a 244473 -n 244473 -f /tmp/ltp-SeaoDkJ1R1/alltests -l /dev/null -C /dev/null -T /dev/null LOG File: /dev/null FAILED COMMAND File: /dev/null TCONF COMMAND File: /dev/null Running tests... tst_test.c:1690: TINFO: LTP version: 20230929-185-g19ef6521d tst_test.c:1574: TINFO: Timeout per run is 0h 00m 30s Test timeouted, sending SIGKILL! tst_test.c:1622: TINFO: Killed the leftover descendant processes tst_test.c:1628: TINFO: If you are running on slow machine, try exporting LTP_TIMEOUT_MUL > 1 tst_test.c:1630: TBROK: Test killed! (timeout?) Summary: passed 0 failed 0 broken 1 skipped 0 warnings 0 INFO: ltp-pan reported some tests FAIL LTP Version: 20230929-185-g19ef6521d INFO: Test end time: Thu Dec 21 09:13:15 UTC 2023 - I tried to test this manually on scobee-kernel, but I found this is a - bit flaky. In some attempts this test can finish with 10 seconds, but - sometimes it will take up to 90 seconds. + And it looks like this test will trigger a warning on this system even if the test has passed: + [ 165.551988] [ cut here ] + [ 165.552018] WARNING: CPU: 0 PID: 15 at kernel/sched/core.c:3109 set_task_cpu+0x168/0x244 + [ 165.552083] Modules linked in: binfmt_misc nls_iso8859_1 ipmi_ssif arm_spe_pmu acpi_ipmi hisi_zip ipmi_si hns_roce_hw_v2 hisi_sec2 hisi_hpre ecdh_generic libcurve25519_generic ipmi_devintf ecc hisi_qm ipmi_msghandler authenc uacce hisi_uncore_l3c_pmu hisi_uncore_hha_pmu hisi_uncore_ddrc_pmu hisi_trng_v2 hisi_uncore_pmu cppc_cpufreq sch_fq_codel dm_multipath scsi_dh_rdac scsi_dh_emc scsi_dh_alua efi_pstore ip_tables x_tables autofs4 btrfs blake2b_generic zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor xor_neon raid6_pq libcrc32c raid1 raid0 multipath linear ses enclosure mlx5_ib ib_uverbs ib_core hibmc_drm drm_vram_helper drm_ttm_helper ttm i2c_algo_bit drm_kms_helper syscopyarea sysfillrect mlx5_core sysimgblt fb_sys_fops cec rc_core mlxfw realtek crct10dif_ce ghash_ce sha2_ce sha256_arm64 sha1_ce hisi_sas_v3_hw hns3 psample hisi_sas_main hclge tls xhci_pci libsas drm hnae3 xhci_pci_renesas ahci scsi_transport_sas spi_dw_mmio spi_dw gp io_dwapb + [ 165.552555] aes_neon_bs aes_neon_blk aes_ce_blk crypto_simd cryptd aes_ce_cipher + [ 165.552595] CPU: 0 PID: 15 Comm: ksoftirqd/0 Not tainted 5.15.0-1052-realtime #58-Ubuntu + [ 165.552614] Hardware name: Huawei TaiShan 2280 V2/BC82AMDC, BIOS 2280-V2 CS V3.B160.01 01/15/2020 + [ 165.552624] pstate: 604000c9 (nZCv daIF +PAN -UAO -TCO -DIT -SSBS BTYPE=--) + [ 165.552641] pc : set_task_cpu+0x168/0x244 + [ 165.552660] lr : detach_tasks+0x138/0x4b0 + [ 165.552684] sp : 8860ba20 + [ 165.552692] x29: 8860ba20 x28: 2020075ac300 x27: a9913540a928 + [ 165.552718] x26: a99134c794c0 x25: a99134c794c0 x24: 003f7fbd9fb0 + [ 165.552739] x23: 0001 x22: 003f7fbd94c0 x21: a99135407a18 + [ 165.552761] x20: 000d x19: 2020075ac300 x18: + [ 165.552784] x17: 56ae4adda000 x16: a99133a3e780 x15: 3d094ed85380 + [ 165.552805] x14: a9913543a5a8 x13: a9913543a078 x12: 000d + [ 165.552828] x11: 0004 x10: a99135407b50 x9 : a99132e30dd8 + [ 165.552846] x8 : 000d x7 : e000 x6 : 0314 + [ 165.552866] x5 : 00532ae2 x4 : 0001 x3 : b67e + [ 165.552886] x2 : x1 : a991344399b8 x0 : 0001 + [ 165.552908] Call trace: + [ 165.552915] set_task_cpu+0x168/0x244 + [ 165.552933] detach_tasks+0x138/0x4b0 + [ 165.552948] load_balance+0x260/0x834 + [ 165.552967] rebalance_domains+0x280/0x3f4 + [ 165.552984] _nohz_idle_balance.constprop.0.isra.0+0x1ec/0x34c + [ 165.553004] run_rebalance_domains+0x84/0xb0 + [ 165.553022] __do_softirq+0x170/0x468 + [ 165.553035] run_ksoftirqd+0x80/0x150 + [ 165.553052] smpboot_thread_fn+0x260/0x2e4 + [ 165.553072] kthread+0x158/0x16c + [ 165.553092] ret_from_fork+0x10/0x20 + [ 165.553117] ---[ end trace 0002 ]--- + + I tried to test this manually on scobee-kernel, but I found this is a bit flaky. In some attempts this test can finish with 10 seconds, but sometimes it will take up to 90 seconds. Maybe bumping the timeout multiplier can be a possible solution. [1] https://lists.ubuntu.com/archives/kernel- team/2023-December/147590.html ** Summary changed: - mm:cpuset01 from ubuntu_ltp flaky on scobee-kernel with J-realtime + mm:cpuset01 from ubuntu_ltp flaky on scobee-kernel with
[Canonical-ubuntu-qa] [Bug 2021908] Re: fwupd: network-based tests failed to run
[Expired for Auto Package Testing because there has been no activity for 60 days.] ** Changed in: auto-package-testing Status: Incomplete => Expired -- You received this bug notification because you are a member of Canonical's Ubuntu QA, which is subscribed to Auto Package Testing. https://bugs.launchpad.net/bugs/2021908 Title: fwupd: network-based tests failed to run Status in Auto Package Testing: Expired Status in fwupd package in Ubuntu: Won't Fix Bug description: `fwupd` package added network-based tests (to test whether firmware updates could be performed) since version 1.9.1. The tests failed due to the HTTP proxy blocklist (which needs access to cdn.fwupd.org). The issue was discovered in the local runner with these log lines: ..snip failed to download http://cdn.fwupd.org/downloads/01b95b0206f1a42a2bf95a432d162ef1f9f1f71edb5696127c923ceffadfdf68-a3bu-xplained123.zip: Failed to download, server response was 403: http://www.w3.org/TR/html4/strict.dtd";> ERROR: The requested URL could not be retrieved In the Ubuntu-hosted autopkgtest runners, it failed with a cryptic message: ...snip failed to load emulation data: emulation is not allowed from config FAIL: fwupd/fwupd.test (Child process exited with code 1) To manage notifications about this bug go to: https://bugs.launchpad.net/auto-package-testing/+bug/2021908/+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
