From: Platform Team regression test user <citrix-osstest@xenproject.org>
To: xen-devel@lists.xensource.com, osstest-admin@xenproject.org
Subject: [ovmf baseline-only test] 71267: trouble: blocked/broken
Date: Tue, 9 May 2017 11:24:41 +0100 [thread overview]
Message-ID: <osstest-71267-mainreport@xen.org> (raw)
This run is configured for baseline tests only.
flight 71267 ovmf real [real]
http://osstest.xs.citrite.net/~osstest/testlogs/logs/71267/
Failures and problems with tests :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-i386-xsm 3 host-install(3) broken REGR. vs. 71264
build-i386-pvops 3 host-install(3) broken REGR. vs. 71264
build-i386 3 host-install(3) broken REGR. vs. 71264
Regressions which are regarded as allowable (not blocking):
build-amd64-xsm 3 host-install(3) broken like 71264
build-amd64 3 host-install(3) broken like 71264
build-amd64-pvops 3 host-install(3) broken like 71264
Tests which did not succeed, but are not blocking:
test-amd64-amd64-xl-qemuu-ovmf-amd64 1 build-check(1) blocked n/a
build-amd64-libvirt 1 build-check(1) blocked n/a
test-amd64-i386-xl-qemuu-ovmf-amd64 1 build-check(1) blocked n/a
build-i386-libvirt 1 build-check(1) blocked n/a
version targeted for testing:
ovmf ca12a0c83b7b889fc807cb2dd47356f0fd1253d6
baseline version:
ovmf 3654c4623c9b37ddc64426995fa399d8626b7ced
Last test of basis 71264 2017-05-08 08:17:59 Z 1 days
Testing same since 71267 2017-05-09 04:46:38 Z 0 days 1 attempts
------------------------------------------------------------
People who touched revisions under test:
Andrey Tepin <atepin@kraftway.ru>
Fu Siyuan <siyuan.fu@intel.com>
jobs:
build-amd64-xsm broken
build-i386-xsm broken
build-amd64 broken
build-i386 broken
build-amd64-libvirt blocked
build-i386-libvirt blocked
build-amd64-pvops broken
build-i386-pvops broken
test-amd64-amd64-xl-qemuu-ovmf-amd64 blocked
test-amd64-i386-xl-qemuu-ovmf-amd64 blocked
------------------------------------------------------------
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
broken-step build-i386-xsm host-install(3)
broken-step build-i386-pvops host-install(3)
broken-step build-i386 host-install(3)
broken-step build-amd64-xsm host-install(3)
broken-step build-amd64 host-install(3)
broken-step build-amd64-pvops host-install(3)
Push not applicable.
------------------------------------------------------------
commit ca12a0c83b7b889fc807cb2dd47356f0fd1253d6
Author: Fu Siyuan <siyuan.fu@intel.com>
Date: Wed May 3 15:22:08 2017 +0800
MdeModulePkg: Addressing TCP Window Retraction when window scale factor is used.
The RFC1323 which defines the TCP window scale option has been obsoleted by RFC7323.
This patch is to follow the RFC7323 to address the TCP window retraction problem
when a non-zero scale factor is used.
The changes has been test in high packet loss rate network by using HTTP boot and
iSCSI file read/write.
Contributed-under: TianoCore Contribution Agreement 1.0
Signed-off-by: Fu Siyuan <siyuan.fu@intel.com>
Reviewed-by: Wu Jiaxin <jiaxin.wu@intel.com>
Reviewed-by: Ye Ting <ting.ye@intel.com>
commit 3696ceaecb03fc8d66988649506f5f22a6526d1e
Author: Fu Siyuan <siyuan.fu@intel.com>
Date: Wed May 3 14:30:36 2017 +0800
NetworkPkg: Addressing TCP Window Retraction when window scale factor is used.
The RFC1323 which defines the TCP window scale option has been obsoleted by RFC7323.
This patch is to follow the RFC7323 to address the TCP window retraction problem
when a non-zero scale factor is used.
The changes has been test in high packet loss rate network by using HTTP boot and
iSCSI file read/write.
Contributed-under: TianoCore Contribution Agreement 1.0
Signed-off-by: Fu Siyuan <siyuan.fu@intel.com>
Reviewed-by: Wu Jiaxin <jiaxin.wu@intel.com>
Reviewed-by: Ye Ting <ting.ye@intel.com>
commit 207b3d2b0b7db33bd65e1943a66d7ee9b7132697
Author: Fu Siyuan <siyuan.fu@intel.com>
Date: Wed May 3 15:21:23 2017 +0800
MdeModulePkg: Add wnd scale check before shrinking window.
Moving Right window edge to the left on sender side without additional check
can lead to the TCP deadlock, when receiver ACKs proper segment, while sender
discards it for future ACK. To prevent this add check if usable window (or
shrink amount in this case) is bigger then receiver's window scale factor.
Contributed-under: TianoCore Contribution Agreement 1.0
Signed-off-by: Andrey Tepin <atepin@kraftway.ru>
Reviewed-by: Fu Siyuan <siyuan.fu@intel.com>
commit 2d5afbdad1bbe2663917c0b3ad06753bbf128c6c
Author: Fu Siyuan <siyuan.fu@intel.com>
Date: Wed May 3 14:20:56 2017 +0800
NetworkPkg: Add wnd scale check before shrinking window.
Moving Right window edge to the left on sender side without additional check
can lead to the TCP deadlock, when receiver ACKs proper segment, while sender
discards it for future ACK. To prevent this add check if usable window (or
shrink amount in this case) is bigger then receiver's window scale factor.
Contributed-under: TianoCore Contribution Agreement 1.0
Signed-off-by: Andrey Tepin <atepin@kraftway.ru>
Reviewed-by: Fu Siyuan <siyuan.fu@intel.com>
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
reply other threads:[~2017-05-09 10:24 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=osstest-71267-mainreport@xen.org \
--to=citrix-osstest@xenproject.org \
--cc=osstest-admin@xenproject.org \
--cc=xen-devel@lists.xensource.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).