]> git.ipfire.org Git - thirdparty/gcc.git/commit
net: don't fail test if splice fails because pipe2 is missing
authorIan Lance Taylor <ian@gcc.gnu.org>
Tue, 2 Oct 2018 15:07:14 +0000 (15:07 +0000)
committerIan Lance Taylor <ian@gcc.gnu.org>
Tue, 2 Oct 2018 15:07:14 +0000 (15:07 +0000)
commit4913fc07e0b3f1d574dc20f83ec819a26ab4346e
treea71fa364340b23c6320039a6aa0951d3decfb01f
parent0036218b1093a36a67d7c04834e5c0383eda6efa
net: don't fail test if splice fails because pipe2 is missing

    This reportedly happens on CentOS 5.11.  The real code will work fine;
    this test is assuming that the unexported slice function will handle
    the splice, but if pipe2 does not work then it doesn't.  The relevant
    code in internal/poll/splice_linux.go says "Falling back to pipe is
    possible, but prior to 2.6.29 splice returns -EAGAIN instead of 0 when
    the connection is closed."

    Reviewed-on: https://go-review.googlesource.com/138838

From-SVN: r264793
gcc/go/gofrontend/MERGE
libgo/go/net/splice_test.go