[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [seabios test] 119162: regressions - trouble: blocked/broken/fail/pass
flight 119162 seabios real [real] http://logs.test-lab.xenproject.org/osstest/logs/119162/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: build-amd64-libvirt <job status> broken build-amd64-libvirt 4 host-install(4) broken REGR. vs. 115539 test-amd64-amd64-xl-qemuu-ws16-amd64 17 guest-stop fail REGR. vs. 115539 Tests which did not succeed, but are not blocking: test-amd64-amd64-libvirt-qemuu-debianhvm-amd64-xsm 1 build-check(1) blocked n/a test-amd64-i386-xl-qemuu-win7-amd64 17 guest-stop fail like 115539 test-amd64-amd64-xl-qemuu-win7-amd64 17 guest-stop fail like 115539 test-amd64-i386-xl-qemuu-ws16-amd64 17 guest-stop fail like 115539 test-amd64-i386-libvirt-qemuu-debianhvm-amd64-xsm 11 migrate-support-check fail never pass test-amd64-amd64-qemuu-nested-amd 17 debian-hvm-install/l1/l2 fail never pass test-amd64-amd64-xl-qemuu-win10-i386 10 windows-install fail never pass test-amd64-i386-xl-qemuu-win10-i386 10 windows-install fail never pass version targeted for testing: seabios 4a6dbcea3e412fe12effa2f812f50dd7eae90955 baseline version: seabios 0ca6d6277dfafc671a5b3718cbeb5c78e2a888ea Last test of basis 115539 2017-11-03 20:48:58 Z 102 days Failing since 115733 2017-11-10 17:19:59 Z 96 days 121 attempts Testing same since 118668 2018-02-08 04:50:43 Z 6 days 9 attempts ------------------------------------------------------------ People who touched revisions under test: Kevin O'Connor <kevin@xxxxxxxxxxxx> Marcel Apfelbaum <marcel@xxxxxxxxxx> Michael S. Tsirkin <mst@xxxxxxxxxx> Nikolay Nikolov <nickysn@xxxxxxxxxxxxxxxxxxxxx> Paul Menzel <pmenzel@xxxxxxxxxxxxx> Stefan Berger <stefanb@xxxxxxxxxxxxxxxxxx> jobs: build-amd64-xsm pass build-i386-xsm pass build-amd64 pass build-i386 pass build-amd64-libvirt broken build-i386-libvirt pass build-amd64-pvops pass build-i386-pvops pass test-amd64-amd64-libvirt-qemuu-debianhvm-amd64-xsm blocked test-amd64-i386-libvirt-qemuu-debianhvm-amd64-xsm pass test-amd64-amd64-xl-qemuu-debianhvm-amd64-xsm pass test-amd64-i386-xl-qemuu-debianhvm-amd64-xsm pass test-amd64-amd64-qemuu-nested-amd fail test-amd64-i386-qemuu-rhel6hvm-amd pass test-amd64-amd64-xl-qemuu-debianhvm-amd64 pass test-amd64-i386-xl-qemuu-debianhvm-amd64 pass test-amd64-amd64-xl-qemuu-win7-amd64 fail test-amd64-i386-xl-qemuu-win7-amd64 fail test-amd64-amd64-xl-qemuu-ws16-amd64 fail test-amd64-i386-xl-qemuu-ws16-amd64 fail test-amd64-amd64-xl-qemuu-win10-i386 fail test-amd64-i386-xl-qemuu-win10-i386 fail test-amd64-amd64-qemuu-nested-intel pass test-amd64-i386-qemuu-rhel6hvm-intel 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 broken-job build-amd64-libvirt broken broken-step build-amd64-libvirt host-install(4) Not pushing. ------------------------------------------------------------ commit 4a6dbcea3e412fe12effa2f812f50dd7eae90955 Author: Nikolay Nikolov <nickysn@xxxxxxxxxxxxxxxxxxxxx> Date: Sun Feb 4 17:27:01 2018 +0200 floppy: Use timer_check() in floppy_wait_irq() Use timer_check() instead of using floppy_motor_counter in BDA for the timeout check in floppy_wait_irq(). The problem with using floppy_motor_counter was that, after it reaches 0, it immediately stops the floppy motors, which is not what is supposed to happen on real hardware. Instead, after a timeout (like in the end of every floppy operation, regardless of the result - success, timeout or error), the floppy motors must be kept spinning for additional 2 seconds (the FLOPPY_MOTOR_TICKS). So, now the floppy_motor_counter is initialized to 255 (the max value) in the beginning of the floppy operation. For IRQ timeouts, a different timeout is used, specified by the new FLOPPY_IRQ_TIMEOUT constant (currently set to 5 seconds - a fairly conservative value, but should work reliably on most floppies). After the floppy operation, floppy_drive_pio() resets the floppy_motor_counter to 2 seconds (FLOPPY_MOTOR_TICKS). This is also consistent with what other PC BIOSes do. Signed-off-by: Nikolay Nikolov <nickysn@xxxxxxxxxxxxxxxxxxxxx> commit 488ede2297461af9d60dd21cff853a49afdc2c70 Author: Nikolay Nikolov <nickysn@xxxxxxxxxxxxxxxxxxxxx> Date: Sun Feb 4 17:27:00 2018 +0200 floppy: Reset the floppy motor count in floppy_drive_pio() Reset the floppy motor count, so the motor keeps spinning 2 seconds after a floppy operation, performed by floppy_drive_pio(). Signed-off-by: Nikolay Nikolov <nickysn@xxxxxxxxxxxxxxxxxxxxx> commit 53d82f0ee8eba571689f64b748bca8e9badda8b2 Author: Nikolay Nikolov <nickysn@xxxxxxxxxxxxxxxxxxxxx> Date: Sun Feb 4 17:26:59 2018 +0200 floppy: Preserve motor and drive sel bits when resetting the floppy controller In case of read or write errors, the floppy system is usually reset and the operation is retried. In that case, the floppy motor state must be preserved in order to avoid creating jitter and keep the floppy motor spinning smoothly at a constant speed. Additionally, the drive select bits should probably also be preserved, because some systems might need a small delay after selecting a new drive. In that case, the operation would be retried, without changing the currently selected drive. In floppy_enable_controller(), the IRQ bit is now enabled first, before the reset bit is set. I'm not completely sure whether this is necessary. It is done just in case some hardware introduces a delay between setting this bit and actually enabling the IRQ, which would cause us to miss the IRQ, sent by the controller immediately after reset. Signed-off-by: Nikolay Nikolov <nickysn@xxxxxxxxxxxxxxxxxxxxx> commit 53fc631307b2c4a403e183afcc5ffe27987349a6 Author: Nikolay Nikolov <nickysn@xxxxxxxxxxxxxxxxxxxxx> Date: Sun Feb 4 17:26:58 2018 +0200 floppy: Introduce FLOPPY_DOR_XXX constants Signed-off-by: Nikolay Nikolov <nickysn@xxxxxxxxxxxxxxxxxxxxx> commit 5157a7882de8b50c2365fd9166c5d91861a478a2 Author: Nikolay Nikolov <nickysn@xxxxxxxxxxxxxxxxxxxxx> Date: Sun Feb 4 17:26:57 2018 +0200 floppy: Introduce floppy_dor_mask() Signed-off-by: Nikolay Nikolov <nickysn@xxxxxxxxxxxxxxxxxxxxx> commit 3ddb42f38f5054aa6eed7971f10da0adc076c74e Author: Nikolay Nikolov <nickysn@xxxxxxxxxxxxxxxxxxxxx> Date: Sun Feb 4 17:26:56 2018 +0200 floppy: Introduce the floppy_dor_read() function Signed-off-by: Nikolay Nikolov <nickysn@xxxxxxxxxxxxxxxxxxxxx> commit 14d91c353e19b7085fdbb7b2dcc43f3355665670 Author: Marcel Apfelbaum <marcel@xxxxxxxxxx> Date: Thu Jan 11 22:15:12 2018 +0200 pci: fix 'io hints' capability for RedHat PCI bridges Commit ec6cb17f (pci: enable RedHat PCI bridges to reserve additional resources on PCI init) added a new vendor specific PCI capability for RedHat PCI bridges allowing them to reserve additional buses and/or IO/MEM space. When adding the IO hints PCI capability to the pcie-root-port without specifying a value for bus reservation, the subordinate bus computation is wrong and the guest kernel gets messed up. Fix it by returning to prev code if the value for bus reservation is not set. Removed also a wrong debug print "PCI: invalid QEMU resource reserve cap offset" which appears if the 'IO hints' capability is not present. Acked-by: Michael S. Tsirkin <mst@xxxxxxxxxx> Signed-off-by: Marcel Apfelbaum <marcel@xxxxxxxxxx> commit 844b86464a5cbfffb62b87808632018ca250d867 Author: Paul Menzel <pmenzel@xxxxxxxxxxxxx> Date: Mon Oct 2 08:13:13 2017 +0200 docs/Download: Use more secure HTTPS URLs where possible Signed-off-by: Paul Menzel <pmenzel@xxxxxxxxxxxxx> commit df46d10c8a7b88eb82f3ceb2aa31782dee15593d Author: Stefan Berger <stefanb@xxxxxxxxxxxxxxxxxx> Date: Tue Nov 14 15:03:47 2017 -0500 tpm: Add support for TPM2 ACPI table Add support for the TPM2 ACPI table. If we find it and its of the appropriate size, we can get the log_area_start_address and log_area_minimum_size from it. The latest version of the spec can be found here: https://trustedcomputinggroup.org/tcg-acpi-specification/ Signed-off-by: Stefan Berger <stefanb@xxxxxxxxxxxxxxxxxx> commit 0541f2f0f246e77d7c726926976920e8072d1119 Author: Kevin O'Connor <kevin@xxxxxxxxxxxx> Date: Fri Nov 10 12:20:35 2017 -0500 paravirt: Only enable sercon in NOGRAPHIC mode if no other console specified Signed-off-by: Kevin O'Connor <kevin@xxxxxxxxxxxx> commit 9ce6778f08c632c52b25bc8f754291ef18710d53 Author: Kevin O'Connor <kevin@xxxxxxxxxxxx> Date: Fri Nov 10 12:16:36 2017 -0500 docs: Add sercon-port to Runtime_config.md documentation Signed-off-by: Kevin O'Connor <kevin@xxxxxxxxxxxx> commit 63451fca13c75870e1703eb3e20584d91179aebc Author: Kevin O'Connor <kevin@xxxxxxxxxxxx> Date: Fri Nov 10 11:49:19 2017 -0500 docs: Note v1.11.0 release Signed-off-by: Kevin O'Connor <kevin@xxxxxxxxxxxx> _______________________________________________ osstest-output mailing list osstest-output@xxxxxxxxxxxxxxxxxxxx https://lists.xenproject.org/mailman/listinfo/osstest-output
|
Lists.xenproject.org is hosted with RackSpace, monitoring our |