[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [xen-unstable-smoke test] 185770: regressions - FAIL
flight 185770 xen-unstable-smoke real [real] flight 185772 xen-unstable-smoke real-retest [real] http://logs.test-lab.xenproject.org/osstest/logs/185770/ http://logs.test-lab.xenproject.org/osstest/logs/185772/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: test-armhf-armhf-xl 8 xen-boot fail REGR. vs. 185760 Tests which did not succeed, but are not blocking: test-amd64-amd64-libvirt 15 migrate-support-check fail never pass test-arm64-arm64-xl-xsm 15 migrate-support-check fail never pass test-arm64-arm64-xl-xsm 16 saverestore-support-check fail never pass version targeted for testing: xen 77e25f0e30ddd11e043e6fce84bf108ce7de5b6f baseline version: xen cccb7878f386fb8691b7e28957a562a66d9b875f Last test of basis 185760 2024-04-22 14:02:06 Z 1 days Testing same since 185770 2024-04-23 13:00:23 Z 0 days 1 attempts ------------------------------------------------------------ People who touched revisions under test: Anthony PERARD <anthony.perard@xxxxxxxxxx> Jan Beulich <jbeulich@xxxxxxxx> Leigh Brown <leigh@xxxxxxxxxxxxx> Roger Pau Monné <roger.pau@xxxxxxxxxx> Ross Lagerwall <ross.lagerwall@xxxxxxxxxx> jobs: build-arm64-xsm pass build-amd64 pass build-armhf pass build-amd64-libvirt pass test-armhf-armhf-xl fail test-arm64-arm64-xl-xsm pass test-amd64-amd64-xl-qemuu-debianhvm-amd64 pass test-amd64-amd64-libvirt pass ------------------------------------------------------------ sg-report-flight on osstest.test-lab.xenproject.org logs: /home/logs/logs images: /home/logs/images Logs, config files, etc. are available at http://logs.test-lab.xenproject.org/osstest/logs Explanation of these reports, and of osstest in general, is at http://xenbits.xen.org/gitweb/?p=osstest.git;a=blob;f=README.email;hb=master http://xenbits.xen.org/gitweb/?p=osstest.git;a=blob;f=README;hb=master Test harness code can be found at http://xenbits.xen.org/gitweb?p=osstest.git;a=summary Not pushing. ------------------------------------------------------------ commit 77e25f0e30ddd11e043e6fce84bf108ce7de5b6f Author: Jan Beulich <jbeulich@xxxxxxxx> Date: Tue Apr 23 14:13:48 2024 +0200 x86/MTRR: correct inadvertently inverted WC check The ! clearly got lost by mistake. Fixes: e9e0eb30d4d6 ("x86/MTRR: avoid several indirect calls") Reported-by: Marek Marczykowski-Górecki <marmarek@xxxxxxxxxxxxxxxxxxxxxx> Signed-off-by: Jan Beulich <jbeulich@xxxxxxxx> Acked-by: Roger Pau Monné <roger.pau@xxxxxxxxxx> commit f82c43a384913460892d4917d2a2f8c2b9399a5e Author: Roger Pau Monné <roger.pau@xxxxxxxxxx> Date: Tue Apr 23 14:12:04 2024 +0200 xen: introduce header file with section related symbols Start by declaring the beginning and end of the init section. No functional change intended. Requested-by: Andrew Cooper <andrew.cooper3@xxxxxxxxxx> Signed-off-by: Roger Pau Monné <roger.pau@xxxxxxxxxx> Reviewed-by: Andrew Cooper <andrew.cooper3@xxxxxxxxxx> commit 70d46b51e2f80f808c91f264f501cca1ca7af2b5 Author: Leigh Brown <leigh@xxxxxxxxxxxxx> Date: Tue Apr 23 14:11:14 2024 +0200 docs/man: Add xenwatchdog manual page Add a manual page for xenwatchdogd. Signed-off-by: Leigh Brown <leigh@xxxxxxxxxxxxx> Reviewed-by: Anthony PERARD <anthony.perard@xxxxxxxxxx> commit 9c872b5766cde6cd9ebeb724a346aaee16e87c84 Author: Leigh Brown <leigh@xxxxxxxxxxxxx> Date: Tue Apr 23 14:10:16 2024 +0200 tools/misc: Add xenwatchdogd.c copyright notice Add copyright notice and description of the program. Signed-off-by: Leigh Brown <leigh@xxxxxxxxxxxxx> Acked-by: Anthony PERARD <anthony.perard@xxxxxxxxxx> commit e906bfae48b2f71607159e7f5589cb71f961351c Author: Leigh Brown <leigh@xxxxxxxxxxxxx> Date: Tue Apr 23 14:10:03 2024 +0200 tools/misc: xenwatchdogd enhancements Add usage() function, the ability to run in the foreground, and the ability to disarm the watchdog timer when exiting. Add enhanced parameter parsing and validation, making use of getopt_long(). Check the number of parameters are correct, the timeout is at least two seconds (to allow a minimum sleep time of one second), and that the sleep time is at least one and less than the watchdog timeout. With these changes, the daemon will no longer instantly reboot the domain if you enter a zero timeout (or non-numeric parameter), and prevent the daemon consuming 100% of a CPU due to zero sleep time. Signed-off-by: Leigh Brown <leigh@xxxxxxxxxxxxx> Reviewed-by: Anthony PERARD <anthony.perard@xxxxxxxxxx> commit f0fa75c9ea9f03cf2c6f5e63d07664ca4b224dd6 Author: Leigh Brown <leigh@xxxxxxxxxxxxx> Date: Tue Apr 23 14:09:50 2024 +0200 tools/misc: xenwatchdogd: add parse_secs() Create a new parse_secs() function to parse the timeout and sleep parameters. This ensures that non-numeric parameters are not accidentally treated as numbers. Signed-off-by: Leigh Brown <leigh@xxxxxxxxxxxxx> Reviewed-by: Anthony PERARD <anthony.perard@xxxxxxxxxx> commit 43a07069863b419433dee12c9b58c1f7ce70aa97 Author: Ross Lagerwall <ross.lagerwall@xxxxxxxxxx> Date: Tue Apr 23 14:09:18 2024 +0200 x86/rtc: Avoid UIP flag being set for longer than expected In a test, OVMF reported an error initializing the RTC without indicating the precise nature of the error. The only plausible explanation I can find is as follows: As part of the initialization, OVMF reads register C and then reads register A repatedly until the UIP flag is not set. If this takes longer than 100 ms, OVMF fails and reports an error. This may happen with the following sequence of events: At guest time=0s, rtc_init() calls check_update_timer() which schedules update_timer for t=(1 - 244us). At t=1s, the update_timer function happens to have been called >= 244us late. In the timer callback, it sets the UIP flag and schedules update_timer2 for t=1s. Before update_timer2 runs, the guest reads register C which calls check_update_timer(). check_update_timer() stops the scheduled update_timer2 and since the guest time is now outside of the update cycle, it schedules update_timer for t=(2 - 244us). The UIP flag will therefore be set for a whole second from t=1 to t=2 while the guest repeatedly reads register A waiting for the UIP flag to clear. Fix it by clearing the UIP flag when scheduling update_timer. I was able to reproduce this issue with a synthetic test and this resolves the issue. Signed-off-by: Ross Lagerwall <ross.lagerwall@xxxxxxxxxx> Reviewed-by: Jan Beulich <jbeulich@xxxxxxxx> (qemu changes not included)
|
Lists.xenproject.org is hosted with RackSpace, monitoring our |