You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
--- FAIL: TestQueryContext (0.01s)
sql_test.go:330: free conns after query hitting EOF = 0; want 1
sql_test.go:156: 1 connections still open after closing DB
FAIL
FAIL database/sql 0.901s
I don't think this is a critical issue in the sql code itself. I think this is an issue in how the test is implemented. The check for number of conns in the DB pool has often been an issue when constructing the test. Due to how the conn pool is constructed (uses non-blocking channels internally) it is not deterministic in the behavior.
This may not be go1.8 worthy.
The text was updated successfully, but these errors were encountered:
From
https://build.golang.org/log/73f2669c736381aa9b2e345f9a582972a493929d
https://build.golang.org/log/5a47d23e13e67143640eeed8f231506a6bae927e
both mips hosts.
https://build.golang.org/log/ffb549b79f60b89283776a265cad961797cd39a1
from arm.
I don't think this is a critical issue in the sql code itself. I think this is an issue in how the test is implemented. The check for number of conns in the DB pool has often been an issue when constructing the test. Due to how the conn pool is constructed (uses non-blocking channels internally) it is not deterministic in the behavior.
This may not be go1.8 worthy.
The text was updated successfully, but these errors were encountered: