FAQ
It seems that go version "08462805eb2c tip" is failing with "Debian
GNU/Linux 3.2.0-4-rt-amd64" but not with "3.2.0-4-amd64" when I call
./all.bash after a clean clone. Any comments? cheers. d

--

Search Discussions

  • Rémy Oudompheng at Dec 3, 2012 at 11:11 pm

    On 2012/12/4 Dorival Pedroso <dorival.pedroso@gmail.com>:
    It seems that go version "08462805eb2c tip" is failing with "Debian
    GNU/Linux 3.2.0-4-rt-amd64" but not with "3.2.0-4-amd64" when I call
    ./all.bash after a clean clone. Any comments? cheers. d
    Hello,

    You need to explain with more details what the failure is.

    Rémy.

    --
  • Dorival Pedroso at Dec 3, 2012 at 11:16 pm
    sure, here you are the output of ./all.bash with the rt kernel:

    ok math/rand 0.032s
    ok mime 0.028s
    ok mime/multipart 0.198s
    --- FAIL: TestDialTimeoutFDLeak-16 (0.51 seconds)
    dial_test.go:260: 134 good connects; expected at most 133
    dial_test.go:260: 135 good connects; expected at most 133
    dial_test.go:260: 136 good connects; expected at most 133
    dial_test.go:260: 137 good connects; expected at most 133
    dial_test.go:260: 138 good connects; expected at most 133
    dial_test.go:260: 139 good connects; expected at most 133
    dial_test.go:260: 140 good connects; expected at most 133
    dial_test.go:260: 141 good connects; expected at most 133
    dial_test.go:260: 142 good connects; expected at most 133
    dial_test.go:260: 143 good connects; expected at most 133
    dial_test.go:260: 144 good connects; expected at most 133
    dial_test.go:260: 145 good connects; expected at most 133
    dial_test.go:260: 146 good connects; expected at most 133
    dial_test.go:260: 147 good connects; expected at most 133
    dial_test.go:260: 148 good connects; expected at most 133
    dial_test.go:260: 149 good connects; expected at most 133
    dial_test.go:260: 150 good connects; expected at most 133
    dial_test.go:260: 151 good connects; expected at most 133
    dial_test.go:260: 152 good connects; expected at most 133
    dial_test.go:260: 153 good connects; expected at most 133
    dial_test.go:260: 154 good connects; expected at most 133
    dial_test.go:260: 155 good connects; expected at most 133
    dial_test.go:260: 156 good connects; expected at most 133
    dial_test.go:260: 157 good connects; expected at most 133
    dial_test.go:260: 158 good connects; expected at most 133
    dial_test.go:260: 159 good connects; expected at most 133
    dial_test.go:260: 160 good connects; expected at most 133
    dial_test.go:260: 161 good connects; expected at most 133
    dial_test.go:260: 162 good connects; expected at most 133
    dial_test.go:260: 163 good connects; expected at most 133
    dial_test.go:260: 164 good connects; expected at most 133
    dial_test.go:260: 165 good connects; expected at most 133
    dial_test.go:260: 166 good connects; expected at most 133
    dial_test.go:260: 167 good connects; expected at most 133
    dial_test.go:260: 168 good connects; expected at most 133
    dial_test.go:260: 169 good connects; expected at most 133
    dial_test.go:260: 170 good connects; expected at most 133
    dial_test.go:260: 171 good connects; expected at most 133
    dial_test.go:260: 172 good connects; expected at most 133
    dial_test.go:260: 173 good connects; expected at most 133
    dial_test.go:260: 174 good connects; expected at most 133
    dial_test.go:260: 175 good connects; expected at most 133
    dial_test.go:260: 176 good connects; expected at most 133
    dial_test.go:260: 177 good connects; expected at most 133
    dial_test.go:260: 178 good connects; expected at most 133
    dial_test.go:260: 179 good connects; expected at most 133
    dial_test.go:260: 180 good connects; expected at most 133
    pollServer WaitFD: epoll_wait: bad file descriptor
    FAIL
    FAIL net 2.309s
    ok net/http 2.533s
    ok net/http/cgi 0.473s





    On Tuesday, December 4, 2012 9:05:01 AM UTC+10, Rémy Oudompheng wrote:

    On 2012/12/4 Dorival Pedroso <dorival...@gmail.com <javascript:>>:
    It seems that go version "08462805eb2c tip" is failing with "Debian
    GNU/Linux 3.2.0-4-rt-amd64" but not with "3.2.0-4-amd64" when I call
    ./all.bash after a clean clone. Any comments? cheers. d
    Hello,

    You need to explain with more details what the failure is.

    Rémy.
    --
  • Dave Cheney at Dec 4, 2012 at 12:06 am
    Sounds similar to http://code.google.com/p/go/issues/detail?id=4384,
    although the underlying issue may not be the same, and may be related
    to the realtime kernel.

    On Tue, Dec 4, 2012 at 10:16 AM, Dorival Pedroso
    wrote:
    sure, here you are the output of ./all.bash with the rt kernel:

    ok math/rand 0.032s
    ok mime 0.028s
    ok mime/multipart 0.198s
    --- FAIL: TestDialTimeoutFDLeak-16 (0.51 seconds)
    dial_test.go:260: 134 good connects; expected at most 133
    dial_test.go:260: 135 good connects; expected at most 133
    dial_test.go:260: 136 good connects; expected at most 133
    dial_test.go:260: 137 good connects; expected at most 133
    dial_test.go:260: 138 good connects; expected at most 133
    dial_test.go:260: 139 good connects; expected at most 133
    dial_test.go:260: 140 good connects; expected at most 133
    dial_test.go:260: 141 good connects; expected at most 133
    dial_test.go:260: 142 good connects; expected at most 133
    dial_test.go:260: 143 good connects; expected at most 133
    dial_test.go:260: 144 good connects; expected at most 133
    dial_test.go:260: 145 good connects; expected at most 133
    dial_test.go:260: 146 good connects; expected at most 133
    dial_test.go:260: 147 good connects; expected at most 133
    dial_test.go:260: 148 good connects; expected at most 133
    dial_test.go:260: 149 good connects; expected at most 133
    dial_test.go:260: 150 good connects; expected at most 133
    dial_test.go:260: 151 good connects; expected at most 133
    dial_test.go:260: 152 good connects; expected at most 133
    dial_test.go:260: 153 good connects; expected at most 133
    dial_test.go:260: 154 good connects; expected at most 133
    dial_test.go:260: 155 good connects; expected at most 133
    dial_test.go:260: 156 good connects; expected at most 133
    dial_test.go:260: 157 good connects; expected at most 133
    dial_test.go:260: 158 good connects; expected at most 133
    dial_test.go:260: 159 good connects; expected at most 133
    dial_test.go:260: 160 good connects; expected at most 133
    dial_test.go:260: 161 good connects; expected at most 133
    dial_test.go:260: 162 good connects; expected at most 133
    dial_test.go:260: 163 good connects; expected at most 133
    dial_test.go:260: 164 good connects; expected at most 133
    dial_test.go:260: 165 good connects; expected at most 133
    dial_test.go:260: 166 good connects; expected at most 133
    dial_test.go:260: 167 good connects; expected at most 133
    dial_test.go:260: 168 good connects; expected at most 133
    dial_test.go:260: 169 good connects; expected at most 133
    dial_test.go:260: 170 good connects; expected at most 133
    dial_test.go:260: 171 good connects; expected at most 133
    dial_test.go:260: 172 good connects; expected at most 133
    dial_test.go:260: 173 good connects; expected at most 133
    dial_test.go:260: 174 good connects; expected at most 133
    dial_test.go:260: 175 good connects; expected at most 133
    dial_test.go:260: 176 good connects; expected at most 133
    dial_test.go:260: 177 good connects; expected at most 133
    dial_test.go:260: 178 good connects; expected at most 133
    dial_test.go:260: 179 good connects; expected at most 133
    dial_test.go:260: 180 good connects; expected at most 133
    pollServer WaitFD: epoll_wait: bad file descriptor
    FAIL
    FAIL net 2.309s
    ok net/http 2.533s
    ok net/http/cgi 0.473s





    On Tuesday, December 4, 2012 9:05:01 AM UTC+10, Rémy Oudompheng wrote:

    On 2012/12/4 Dorival Pedroso <dorival...@gmail.com>:
    It seems that go version "08462805eb2c tip" is failing with "Debian
    GNU/Linux 3.2.0-4-rt-amd64" but not with "3.2.0-4-amd64" when I call
    ./all.bash after a clean clone. Any comments? cheers. d
    Hello,

    You need to explain with more details what the failure is.

    Rémy.
    --
    --
  • Dorival Pedroso at Dec 4, 2012 at 12:14 am
    thanks. i still don't understand it... it's happening with a non-rt kernel
    as well now:


    ok mime 0.016s
    ok mime/multipart 0.197s
    --- FAIL: TestDialTimeoutFDLeak-16 (0.51 seconds)
    dial_test.go:260: 134 good connects; expected at most 133
    dial_test.go:260: 135 good connects; expected at most 133
    dial_test.go:260: 136 good connects; expected at most 133
    dial_test.go:260: 137 good connects; expected at most 133
    dial_test.go:260: 138 good connects; expected at most 133
    dial_test.go:260: 139 good connects; expected at most 133
    dial_test.go:260: 140 good connects; expected at most 133
    dial_test.go:260: 141 good connects; expected at most 133
    dial_test.go:260: 142 good connects; expected at most 133
    dial_test.go:260: 143 good connects; expected at most 133
    dial_test.go:260: 144 good connects; expected at most 133
    dial_test.go:260: 145 good connects; expected at most 133
    pollServer WaitFD: epoll_wait: bad file descriptor
    FAIL
    FAIL net 2.281s


    OK, apparently it happens with GOMAXPROCS=16. i've tried again with
    GOMAXPROCS=2 and it worked...
    cheers.
    d

    On Tuesday, December 4, 2012 10:06:29 AM UTC+10, Dave Cheney wrote:

    Sounds similar to http://code.google.com/p/go/issues/detail?id=4384,
    although the underlying issue may not be the same, and may be related
    to the realtime kernel.

    On Tue, Dec 4, 2012 at 10:16 AM, Dorival Pedroso
    <dorival...@gmail.com <javascript:>> wrote:
    sure, here you are the output of ./all.bash with the rt kernel:

    ok math/rand 0.032s
    ok mime 0.028s
    ok mime/multipart 0.198s
    --- FAIL: TestDialTimeoutFDLeak-16 (0.51 seconds)
    dial_test.go:260: 134 good connects; expected at most 133
    dial_test.go:260: 135 good connects; expected at most 133
    dial_test.go:260: 136 good connects; expected at most 133
    dial_test.go:260: 137 good connects; expected at most 133
    dial_test.go:260: 138 good connects; expected at most 133
    dial_test.go:260: 139 good connects; expected at most 133
    dial_test.go:260: 140 good connects; expected at most 133
    dial_test.go:260: 141 good connects; expected at most 133
    dial_test.go:260: 142 good connects; expected at most 133
    dial_test.go:260: 143 good connects; expected at most 133
    dial_test.go:260: 144 good connects; expected at most 133
    dial_test.go:260: 145 good connects; expected at most 133
    dial_test.go:260: 146 good connects; expected at most 133
    dial_test.go:260: 147 good connects; expected at most 133
    dial_test.go:260: 148 good connects; expected at most 133
    dial_test.go:260: 149 good connects; expected at most 133
    dial_test.go:260: 150 good connects; expected at most 133
    dial_test.go:260: 151 good connects; expected at most 133
    dial_test.go:260: 152 good connects; expected at most 133
    dial_test.go:260: 153 good connects; expected at most 133
    dial_test.go:260: 154 good connects; expected at most 133
    dial_test.go:260: 155 good connects; expected at most 133
    dial_test.go:260: 156 good connects; expected at most 133
    dial_test.go:260: 157 good connects; expected at most 133
    dial_test.go:260: 158 good connects; expected at most 133
    dial_test.go:260: 159 good connects; expected at most 133
    dial_test.go:260: 160 good connects; expected at most 133
    dial_test.go:260: 161 good connects; expected at most 133
    dial_test.go:260: 162 good connects; expected at most 133
    dial_test.go:260: 163 good connects; expected at most 133
    dial_test.go:260: 164 good connects; expected at most 133
    dial_test.go:260: 165 good connects; expected at most 133
    dial_test.go:260: 166 good connects; expected at most 133
    dial_test.go:260: 167 good connects; expected at most 133
    dial_test.go:260: 168 good connects; expected at most 133
    dial_test.go:260: 169 good connects; expected at most 133
    dial_test.go:260: 170 good connects; expected at most 133
    dial_test.go:260: 171 good connects; expected at most 133
    dial_test.go:260: 172 good connects; expected at most 133
    dial_test.go:260: 173 good connects; expected at most 133
    dial_test.go:260: 174 good connects; expected at most 133
    dial_test.go:260: 175 good connects; expected at most 133
    dial_test.go:260: 176 good connects; expected at most 133
    dial_test.go:260: 177 good connects; expected at most 133
    dial_test.go:260: 178 good connects; expected at most 133
    dial_test.go:260: 179 good connects; expected at most 133
    dial_test.go:260: 180 good connects; expected at most 133
    pollServer WaitFD: epoll_wait: bad file descriptor
    FAIL
    FAIL net 2.309s
    ok net/http 2.533s
    ok net/http/cgi 0.473s





    On Tuesday, December 4, 2012 9:05:01 AM UTC+10, Rémy Oudompheng wrote:

    On 2012/12/4 Dorival Pedroso <dorival...@gmail.com>:
    It seems that go version "08462805eb2c tip" is failing with "Debian
    GNU/Linux 3.2.0-4-rt-amd64" but not with "3.2.0-4-amd64" when I call
    ./all.bash after a clean clone. Any comments? cheers. d
    Hello,

    You need to explain with more details what the failure is.

    Rémy.
    --
    --
  • Dave Cheney at Dec 4, 2012 at 12:16 am
    That is the symptom. This test is not stable with high GOMAXPROCS values.

    On Tue, Dec 4, 2012 at 11:14 AM, Dorival Pedroso
    wrote:
    thanks. i still don't understand it... it's happening with a non-rt kernel
    as well now:


    ok mime 0.016s
    ok mime/multipart 0.197s
    --- FAIL: TestDialTimeoutFDLeak-16 (0.51 seconds)
    dial_test.go:260: 134 good connects; expected at most 133
    dial_test.go:260: 135 good connects; expected at most 133
    dial_test.go:260: 136 good connects; expected at most 133
    dial_test.go:260: 137 good connects; expected at most 133
    dial_test.go:260: 138 good connects; expected at most 133
    dial_test.go:260: 139 good connects; expected at most 133
    dial_test.go:260: 140 good connects; expected at most 133
    dial_test.go:260: 141 good connects; expected at most 133
    dial_test.go:260: 142 good connects; expected at most 133
    dial_test.go:260: 143 good connects; expected at most 133
    dial_test.go:260: 144 good connects; expected at most 133
    dial_test.go:260: 145 good connects; expected at most 133
    pollServer WaitFD: epoll_wait: bad file descriptor
    FAIL
    FAIL net 2.281s


    OK, apparently it happens with GOMAXPROCS=16. i've tried again with
    GOMAXPROCS=2 and it worked...
    cheers.
    d

    On Tuesday, December 4, 2012 10:06:29 AM UTC+10, Dave Cheney wrote:

    Sounds similar to http://code.google.com/p/go/issues/detail?id=4384,
    although the underlying issue may not be the same, and may be related
    to the realtime kernel.

    On Tue, Dec 4, 2012 at 10:16 AM, Dorival Pedroso
    wrote:
    sure, here you are the output of ./all.bash with the rt kernel:

    ok math/rand 0.032s
    ok mime 0.028s
    ok mime/multipart 0.198s
    --- FAIL: TestDialTimeoutFDLeak-16 (0.51 seconds)
    dial_test.go:260: 134 good connects; expected at most 133
    dial_test.go:260: 135 good connects; expected at most 133
    dial_test.go:260: 136 good connects; expected at most 133
    dial_test.go:260: 137 good connects; expected at most 133
    dial_test.go:260: 138 good connects; expected at most 133
    dial_test.go:260: 139 good connects; expected at most 133
    dial_test.go:260: 140 good connects; expected at most 133
    dial_test.go:260: 141 good connects; expected at most 133
    dial_test.go:260: 142 good connects; expected at most 133
    dial_test.go:260: 143 good connects; expected at most 133
    dial_test.go:260: 144 good connects; expected at most 133
    dial_test.go:260: 145 good connects; expected at most 133
    dial_test.go:260: 146 good connects; expected at most 133
    dial_test.go:260: 147 good connects; expected at most 133
    dial_test.go:260: 148 good connects; expected at most 133
    dial_test.go:260: 149 good connects; expected at most 133
    dial_test.go:260: 150 good connects; expected at most 133
    dial_test.go:260: 151 good connects; expected at most 133
    dial_test.go:260: 152 good connects; expected at most 133
    dial_test.go:260: 153 good connects; expected at most 133
    dial_test.go:260: 154 good connects; expected at most 133
    dial_test.go:260: 155 good connects; expected at most 133
    dial_test.go:260: 156 good connects; expected at most 133
    dial_test.go:260: 157 good connects; expected at most 133
    dial_test.go:260: 158 good connects; expected at most 133
    dial_test.go:260: 159 good connects; expected at most 133
    dial_test.go:260: 160 good connects; expected at most 133
    dial_test.go:260: 161 good connects; expected at most 133
    dial_test.go:260: 162 good connects; expected at most 133
    dial_test.go:260: 163 good connects; expected at most 133
    dial_test.go:260: 164 good connects; expected at most 133
    dial_test.go:260: 165 good connects; expected at most 133
    dial_test.go:260: 166 good connects; expected at most 133
    dial_test.go:260: 167 good connects; expected at most 133
    dial_test.go:260: 168 good connects; expected at most 133
    dial_test.go:260: 169 good connects; expected at most 133
    dial_test.go:260: 170 good connects; expected at most 133
    dial_test.go:260: 171 good connects; expected at most 133
    dial_test.go:260: 172 good connects; expected at most 133
    dial_test.go:260: 173 good connects; expected at most 133
    dial_test.go:260: 174 good connects; expected at most 133
    dial_test.go:260: 175 good connects; expected at most 133
    dial_test.go:260: 176 good connects; expected at most 133
    dial_test.go:260: 177 good connects; expected at most 133
    dial_test.go:260: 178 good connects; expected at most 133
    dial_test.go:260: 179 good connects; expected at most 133
    dial_test.go:260: 180 good connects; expected at most 133
    pollServer WaitFD: epoll_wait: bad file descriptor
    FAIL
    FAIL net 2.309s
    ok net/http 2.533s
    ok net/http/cgi 0.473s





    On Tuesday, December 4, 2012 9:05:01 AM UTC+10, Rémy Oudompheng wrote:

    On 2012/12/4 Dorival Pedroso <dorival...@gmail.com>:
    It seems that go version "08462805eb2c tip" is failing with "Debian
    GNU/Linux 3.2.0-4-rt-amd64" but not with "3.2.0-4-amd64" when I call
    ./all.bash after a clean clone. Any comments? cheers. d
    Hello,

    You need to explain with more details what the failure is.

    Rémy.
    --
    --
    --
  • Dorival Pedroso at Dec 4, 2012 at 12:17 am
    NO, sorry, it's random... failed again with GOMAXPROCS=2
    On Tuesday, December 4, 2012 10:14:53 AM UTC+10, Dorival Pedroso wrote:

    thanks. i still don't understand it... it's happening with a non-rt kernel
    as well now:


    ok mime 0.016s
    ok mime/multipart 0.197s
    --- FAIL: TestDialTimeoutFDLeak-16 (0.51 seconds)
    dial_test.go:260: 134 good connects; expected at most 133
    dial_test.go:260: 135 good connects; expected at most 133
    dial_test.go:260: 136 good connects; expected at most 133
    dial_test.go:260: 137 good connects; expected at most 133
    dial_test.go:260: 138 good connects; expected at most 133
    dial_test.go:260: 139 good connects; expected at most 133
    dial_test.go:260: 140 good connects; expected at most 133
    dial_test.go:260: 141 good connects; expected at most 133
    dial_test.go:260: 142 good connects; expected at most 133
    dial_test.go:260: 143 good connects; expected at most 133
    dial_test.go:260: 144 good connects; expected at most 133
    dial_test.go:260: 145 good connects; expected at most 133
    pollServer WaitFD: epoll_wait: bad file descriptor
    FAIL
    FAIL net 2.281s


    OK, apparently it happens with GOMAXPROCS=16. i've tried again with
    GOMAXPROCS=2 and it worked...
    cheers.
    d

    On Tuesday, December 4, 2012 10:06:29 AM UTC+10, Dave Cheney wrote:

    Sounds similar to http://code.google.com/p/go/issues/detail?id=4384,
    although the underlying issue may not be the same, and may be related
    to the realtime kernel.

    On Tue, Dec 4, 2012 at 10:16 AM, Dorival Pedroso
    wrote:
    sure, here you are the output of ./all.bash with the rt kernel:

    ok math/rand 0.032s
    ok mime 0.028s
    ok mime/multipart 0.198s
    --- FAIL: TestDialTimeoutFDLeak-16 (0.51 seconds)
    dial_test.go:260: 134 good connects; expected at most 133
    dial_test.go:260: 135 good connects; expected at most 133
    dial_test.go:260: 136 good connects; expected at most 133
    dial_test.go:260: 137 good connects; expected at most 133
    dial_test.go:260: 138 good connects; expected at most 133
    dial_test.go:260: 139 good connects; expected at most 133
    dial_test.go:260: 140 good connects; expected at most 133
    dial_test.go:260: 141 good connects; expected at most 133
    dial_test.go:260: 142 good connects; expected at most 133
    dial_test.go:260: 143 good connects; expected at most 133
    dial_test.go:260: 144 good connects; expected at most 133
    dial_test.go:260: 145 good connects; expected at most 133
    dial_test.go:260: 146 good connects; expected at most 133
    dial_test.go:260: 147 good connects; expected at most 133
    dial_test.go:260: 148 good connects; expected at most 133
    dial_test.go:260: 149 good connects; expected at most 133
    dial_test.go:260: 150 good connects; expected at most 133
    dial_test.go:260: 151 good connects; expected at most 133
    dial_test.go:260: 152 good connects; expected at most 133
    dial_test.go:260: 153 good connects; expected at most 133
    dial_test.go:260: 154 good connects; expected at most 133
    dial_test.go:260: 155 good connects; expected at most 133
    dial_test.go:260: 156 good connects; expected at most 133
    dial_test.go:260: 157 good connects; expected at most 133
    dial_test.go:260: 158 good connects; expected at most 133
    dial_test.go:260: 159 good connects; expected at most 133
    dial_test.go:260: 160 good connects; expected at most 133
    dial_test.go:260: 161 good connects; expected at most 133
    dial_test.go:260: 162 good connects; expected at most 133
    dial_test.go:260: 163 good connects; expected at most 133
    dial_test.go:260: 164 good connects; expected at most 133
    dial_test.go:260: 165 good connects; expected at most 133
    dial_test.go:260: 166 good connects; expected at most 133
    dial_test.go:260: 167 good connects; expected at most 133
    dial_test.go:260: 168 good connects; expected at most 133
    dial_test.go:260: 169 good connects; expected at most 133
    dial_test.go:260: 170 good connects; expected at most 133
    dial_test.go:260: 171 good connects; expected at most 133
    dial_test.go:260: 172 good connects; expected at most 133
    dial_test.go:260: 173 good connects; expected at most 133
    dial_test.go:260: 174 good connects; expected at most 133
    dial_test.go:260: 175 good connects; expected at most 133
    dial_test.go:260: 176 good connects; expected at most 133
    dial_test.go:260: 177 good connects; expected at most 133
    dial_test.go:260: 178 good connects; expected at most 133
    dial_test.go:260: 179 good connects; expected at most 133
    dial_test.go:260: 180 good connects; expected at most 133
    pollServer WaitFD: epoll_wait: bad file descriptor
    FAIL
    FAIL net 2.309s
    ok net/http 2.533s
    ok net/http/cgi 0.473s





    On Tuesday, December 4, 2012 9:05:01 AM UTC+10, Rémy Oudompheng wrote:

    On 2012/12/4 Dorival Pedroso <dorival...@gmail.com>:
    It seems that go version "08462805eb2c tip" is failing with "Debian
    GNU/Linux 3.2.0-4-rt-amd64" but not with "3.2.0-4-amd64" when I call
    ./all.bash after a clean clone. Any comments? cheers. d
    Hello,

    You need to explain with more details what the failure is.

    Rémy.
    --
    --
  • Dave Cheney at Dec 4, 2012 at 12:42 am
    When I say high, i meant GOMAXPROCS!=1

    On Tue, Dec 4, 2012 at 11:17 AM, Dorival Pedroso
    wrote:
    NO, sorry, it's random... failed again with GOMAXPROCS=2

    On Tuesday, December 4, 2012 10:14:53 AM UTC+10, Dorival Pedroso wrote:

    thanks. i still don't understand it... it's happening with a non-rt kernel
    as well now:


    ok mime 0.016s
    ok mime/multipart 0.197s
    --- FAIL: TestDialTimeoutFDLeak-16 (0.51 seconds)
    dial_test.go:260: 134 good connects; expected at most 133
    dial_test.go:260: 135 good connects; expected at most 133
    dial_test.go:260: 136 good connects; expected at most 133
    dial_test.go:260: 137 good connects; expected at most 133
    dial_test.go:260: 138 good connects; expected at most 133
    dial_test.go:260: 139 good connects; expected at most 133
    dial_test.go:260: 140 good connects; expected at most 133
    dial_test.go:260: 141 good connects; expected at most 133
    dial_test.go:260: 142 good connects; expected at most 133
    dial_test.go:260: 143 good connects; expected at most 133
    dial_test.go:260: 144 good connects; expected at most 133
    dial_test.go:260: 145 good connects; expected at most 133
    pollServer WaitFD: epoll_wait: bad file descriptor
    FAIL
    FAIL net 2.281s


    OK, apparently it happens with GOMAXPROCS=16. i've tried again with
    GOMAXPROCS=2 and it worked...
    cheers.
    d

    On Tuesday, December 4, 2012 10:06:29 AM UTC+10, Dave Cheney wrote:

    Sounds similar to http://code.google.com/p/go/issues/detail?id=4384,
    although the underlying issue may not be the same, and may be related
    to the realtime kernel.

    On Tue, Dec 4, 2012 at 10:16 AM, Dorival Pedroso
    wrote:
    sure, here you are the output of ./all.bash with the rt kernel:

    ok math/rand 0.032s
    ok mime 0.028s
    ok mime/multipart 0.198s
    --- FAIL: TestDialTimeoutFDLeak-16 (0.51 seconds)
    dial_test.go:260: 134 good connects; expected at most 133
    dial_test.go:260: 135 good connects; expected at most 133
    dial_test.go:260: 136 good connects; expected at most 133
    dial_test.go:260: 137 good connects; expected at most 133
    dial_test.go:260: 138 good connects; expected at most 133
    dial_test.go:260: 139 good connects; expected at most 133
    dial_test.go:260: 140 good connects; expected at most 133
    dial_test.go:260: 141 good connects; expected at most 133
    dial_test.go:260: 142 good connects; expected at most 133
    dial_test.go:260: 143 good connects; expected at most 133
    dial_test.go:260: 144 good connects; expected at most 133
    dial_test.go:260: 145 good connects; expected at most 133
    dial_test.go:260: 146 good connects; expected at most 133
    dial_test.go:260: 147 good connects; expected at most 133
    dial_test.go:260: 148 good connects; expected at most 133
    dial_test.go:260: 149 good connects; expected at most 133
    dial_test.go:260: 150 good connects; expected at most 133
    dial_test.go:260: 151 good connects; expected at most 133
    dial_test.go:260: 152 good connects; expected at most 133
    dial_test.go:260: 153 good connects; expected at most 133
    dial_test.go:260: 154 good connects; expected at most 133
    dial_test.go:260: 155 good connects; expected at most 133
    dial_test.go:260: 156 good connects; expected at most 133
    dial_test.go:260: 157 good connects; expected at most 133
    dial_test.go:260: 158 good connects; expected at most 133
    dial_test.go:260: 159 good connects; expected at most 133
    dial_test.go:260: 160 good connects; expected at most 133
    dial_test.go:260: 161 good connects; expected at most 133
    dial_test.go:260: 162 good connects; expected at most 133
    dial_test.go:260: 163 good connects; expected at most 133
    dial_test.go:260: 164 good connects; expected at most 133
    dial_test.go:260: 165 good connects; expected at most 133
    dial_test.go:260: 166 good connects; expected at most 133
    dial_test.go:260: 167 good connects; expected at most 133
    dial_test.go:260: 168 good connects; expected at most 133
    dial_test.go:260: 169 good connects; expected at most 133
    dial_test.go:260: 170 good connects; expected at most 133
    dial_test.go:260: 171 good connects; expected at most 133
    dial_test.go:260: 172 good connects; expected at most 133
    dial_test.go:260: 173 good connects; expected at most 133
    dial_test.go:260: 174 good connects; expected at most 133
    dial_test.go:260: 175 good connects; expected at most 133
    dial_test.go:260: 176 good connects; expected at most 133
    dial_test.go:260: 177 good connects; expected at most 133
    dial_test.go:260: 178 good connects; expected at most 133
    dial_test.go:260: 179 good connects; expected at most 133
    dial_test.go:260: 180 good connects; expected at most 133
    pollServer WaitFD: epoll_wait: bad file descriptor
    FAIL
    FAIL net 2.309s
    ok net/http 2.533s
    ok net/http/cgi 0.473s





    On Tuesday, December 4, 2012 9:05:01 AM UTC+10, Rémy Oudompheng wrote:

    On 2012/12/4 Dorival Pedroso <dorival...@gmail.com>:
    It seems that go version "08462805eb2c tip" is failing with "Debian
    GNU/Linux 3.2.0-4-rt-amd64" but not with "3.2.0-4-amd64" when I call
    ./all.bash after a clean clone. Any comments? cheers. d
    Hello,

    You need to explain with more details what the failure is.

    Rémy.
    --
    --
    --

Related Discussions

Discussion Navigation
viewthread | post
Discussion Overview
groupgolang-nuts @
categoriesgo
postedDec 3, '12 at 11:02p
activeDec 4, '12 at 12:42a
posts8
users3
websitegolang.org

People

Translate

site design / logo © 2022 Grokbase