|
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [Xen-devel] [seabios baseline-only test] 68632: tolerable FAIL
This run is configured for baseline tests only. flight 68632 seabios real [real] http://osstest.xs.citrite.net/~osstest/testlogs/logs/68632/ Failures :-/ but no regressions. Regressions which are regarded as allowable (not blocking): test-amd64-amd64-xl-qemuu-win7-amd64 16 guest-stop fail like 68604 test-amd64-i386-xl-qemuu-win7-amd64 16 guest-stop fail like 68604 test-amd64-amd64-qemuu-nested-intel 16 debian-hvm-install/l1/l2 fail like 68604 test-amd64-i386-xl-qemuu-winxpsp3-vcpus1 9 windows-install fail like 68604 Tests which did not succeed, but are not blocking: test-amd64-i386-libvirt-qemuu-debianhvm-amd64-xsm 10 migrate-support-check fail never pass test-amd64-amd64-libvirt-qemuu-debianhvm-amd64-xsm 10 migrate-support-check fail never pass test-amd64-amd64-qemuu-nested-amd 16 debian-hvm-install/l1/l2 fail never pass version targeted for testing: seabios 1415d46dc87fd8bf1d6acd97c1ad60e893f62523 baseline version: seabios 8f598a4641f98cf503653f80c779793d91c95a84 Last test of basis 68604 2017-02-22 20:19:52 Z 9 days Testing same since 68632 2017-03-03 11:20:46 Z 1 days 1 attempts ------------------------------------------------------------ People who touched revisions under test: Daniel Verkamp <daniel@xxxxxx> Kevin O'Connor <kevin@xxxxxxxxxxxx> jobs: build-amd64-xsm pass build-i386-xsm pass build-amd64 pass build-i386 pass build-amd64-libvirt pass build-i386-libvirt pass build-amd64-pvops pass build-i386-pvops pass test-amd64-amd64-libvirt-qemuu-debianhvm-amd64-xsm pass 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-qemuu-nested-intel fail test-amd64-i386-qemuu-rhel6hvm-intel pass test-amd64-i386-xl-qemuu-winxpsp3-vcpus1 fail test-amd64-amd64-xl-qemuu-winxpsp3 pass test-amd64-i386-xl-qemuu-winxpsp3 pass ------------------------------------------------------------ sg-report-flight on osstest.xs.citrite.net logs: /home/osstest/logs images: /home/osstest/images Logs, config files, etc. are available at http://osstest.xs.citrite.net/~osstest/testlogs/logs Test harness code can be found at http://xenbits.xensource.com/gitweb?p=osstest.git;a=summary Push not applicable. ------------------------------------------------------------ commit 1415d46dc87fd8bf1d6acd97c1ad60e893f62523 Author: Daniel Verkamp <daniel@xxxxxx> Date: Thu Feb 23 23:27:57 2017 -0700 nvme: fix copy-paste mistake in comment Signed-off-by: Daniel Verkamp <daniel@xxxxxx> Reviewed-by: Philippe Mathieu-Daudé <f4bug@xxxxxxxxx> commit d8a6c846924df07af2e48796af8b0a0f03e94f9a Author: Daniel Verkamp <daniel@xxxxxx> Date: Thu Feb 23 23:27:56 2017 -0700 nvme: fix extraction of status code bits The status code field is 8 bits wide starting at bit 1; the previous code would truncate the top bit. Signed-off-by: Daniel Verkamp <daniel@xxxxxx> Reviewed-by: Philippe Mathieu-Daudé <f4bug@xxxxxxxxx> commit 2e82b465fbdb46efdc2ebb638aef17fa7f665dc5 Author: Daniel Verkamp <daniel@xxxxxx> Date: Thu Feb 23 23:27:55 2017 -0700 nvme: fix reversed loop condition in cmd_readwrite It looks like the intent was to exit the loop if a command failed, but the current code would actually continue looping in that case. Signed-off-by: Daniel Verkamp <daniel@xxxxxx> Reviewed-by: Philippe Mathieu-Daudé <f4bug@xxxxxxxxx> commit 21de72ffe8dcddf126c136918951c441edf85929 Author: Daniel Verkamp <daniel@xxxxxx> Date: Thu Feb 23 23:27:54 2017 -0700 nvme: extend command timeout to 5 seconds 500 ms is not sufficient for the admin commands used during initialization on some real hardware. Signed-off-by: Daniel Verkamp <daniel@xxxxxx> commit f21e3044a6b8c2195fb243aeb20b3511569e120a Author: Daniel Verkamp <daniel@xxxxxx> Date: Thu Feb 23 23:27:53 2017 -0700 nvme: support NVMe 1.0 controllers Rather than using the Identify command with CNS 01b (GET_NS_LIST), which was added in NVMe 1.1, we can just enumerate all of the possible namespace IDs. The relevant part of the NVMe spec reads: Namespaces shall be allocated in order (starting with 1) and packed sequentially. Since the previously-used GET_NS_LIST only returns active namespaces, we also need a check in nvme_probe_ns() to ensure that inactive namespaces are not reported as boot devices. This can be accomplished by checking for non-zero block count - the spec indicates that Identify Namespace for an inactive namespace ID will return all zeroes. This should have no impact on the QEMU NVMe device model, since it always reports exactly one namespace (NSID 1). Signed-off-by: Daniel Verkamp <daniel@xxxxxx> commit 6bc4164cc8570ed3140d34080e38878adce13593 Author: Kevin O'Connor <kevin@xxxxxxxxxxxx> Date: Thu Mar 2 09:25:12 2017 -0500 docs: Note release dates for 1.10.1 and 1.10.2 Signed-off-by: Kevin O'Connor <kevin@xxxxxxxxxxxx> _______________________________________________ Xen-devel mailing list Xen-devel@xxxxxxxxxxxxx https://lists.xen.org/xen-devel
|
 |
Lists.xenproject.org is hosted with RackSpace, monitoring our |