3
83%
master: 83%

Ran 12 May 2020 04:20AM UTC

Files 17

Run time 2s

Badge

Embed ▾

Committed 12 May 2020 04:12AM UTC coverage: 81.146% (+0.02%) from 81.129%

Job # 1873.3

Build Type

push

travis-ci-com

Committed by

web-flow

Commit Message

Fix checking cancelled connections back into the connection pool (#1095)

If
    * BeginTx is called with a non-default isolation level,
    * The context is canceled before SET TRANSACTION ISOLATION LEVEL
    completes,
then the connection:
    * has the cancelled property set to "context cancelled",
    * has the closed property set to true,
and,
    * BeginTx returns "context canceled"

Because of this, the connection gets put back into the connection pool.
When it is checked out again, if BeginTx is called on it again _without_
an isolation level,
    * then we fall into the mc.closed.IsSet() check in begin(),
    * so we return ErrBadConn,
    * so the driver kicks the broken connection out of the pool
    * (and transparently retries to get a new connection that isn't
    broken too).

However, if BeginTx is called on the connection _with_ an isolation
level, then we return a context canceled error from the SET TRANSACTION
ISOLATION LEVEL call.

That means the broken connection will stick around in the pool forever
(or until it's checked out for some other operation that correctly
returns ErrBadConn).

The fix is to check for the connection being closed before executing SET
TRANSACTION ISOLATION LEVEL.

Run Details

2776 of 3421 relevant lines covered (81.15%)

56908.6 hits per line

go-sql-driver / mysql / 1873 / 3
83%
master: 83%

README BADGES
x

Markdown

Textile

RDoc

HTML

Rst

Source Files on job 1873.3

go-sql-driver / mysql / 1873 / 3 83% master: 83%

README BADGES x

Markdown

Textile

RDoc

HTML

Rst

Source Files on job 1873.3

go-sql-driver / mysql / 1873 / 3
83%
master: 83%

README BADGES
x