Can you also include the stack trace from the CHECK failure?
On Tue, Jun 26, 2018 at 11:25 PM, Suteng wrote:
> F0622 11:22:30.985245 16127 libevent_ssl_socket.cpp:190] Check failed:
> 'self->bev' Must be non NULL
>
> Try LibeventSSLSocketImpl::shutdown(int how)
>
> CHECK_NOTNULL(self->bev)
Hmm. Lot of tests failed when I ran this through ASF CI. Not sure if all of
these are known flaky tests?
Su Teng,
Thank you very much for this bug report! Much appreciated.
Could you provide more information about the environment in which you
noticed the bug originally - was it a running Mesos cluster? Did you use
the provided snippet to reproduce the issue?
Greg
On Tue, Jun 26, 2018 at 11:25 PM,
+1
Passed on our internal CI that has the following matrix. I looked into the
only failed test, looks to be a flaky test due to a race in the test.
On Tue, Jun 26, 2018 at 7:02 PM, Greg Mann wrote:
> Hi all,
>
> Please vote on releasing the following candidate as Apache Mesos 1.6.1.
>
>
>
Do we still need this check? The order of built-in isolators is now fixed, so
do we still need to verify this ordering?
> On Jun 27, 2018, at 4:17 PM, gilb...@apache.org wrote:
>
> Repository: mesos
> Updated Branches:
> refs/heads/master 2e913d545 -> b581136bd
>
>
> Made `gpu/nvidia`
F0622 11:22:30.985245 16127 libevent_ssl_socket.cpp:190] Check failed:
'self->bev' Must be non NULL
Try LibeventSSLSocketImpl::shutdown(int how)
CHECK_NOTNULL(self->bev)
Test case:
A server is non-ssl, B server is enable downgrade, B frequent link reconnect to
A, then will generate this
