1. 29 Jan, 2016 8 commits
  2. 28 Jan, 2016 2 commits
  3. 26 Jan, 2016 2 commits
  4. 22 Jan, 2016 1 commit
  5. 21 Jan, 2016 1 commit
  6. 20 Jan, 2016 2 commits
  7. 19 Jan, 2016 6 commits
  8. 18 Jan, 2016 6 commits
  9. 16 Jan, 2016 3 commits
  10. 15 Jan, 2016 3 commits
    • Brad Fitzpatrick's avatar
      net/http: update bundled http2 · 91b910b7
      Brad Fitzpatrick authored
      If a user starts two HTTP requests when no http2 connection is
      available, both end up creating new TCP connections, since the
      server's protocol (h1 or h2) isn't yet known. Once it turns out that
      the server supports h2, one of the connections is useless. Previously
      we kept upgrading both TLS connections to h2 (SETTINGS frame exchange,
      etc).  Now the unnecessary connections are closed instead, before the
      h2 preface/SETTINGS.
      
      Updates x/net/http2 to git rev a8e212f3d for https://golang.org/cl/18675
      
      This CL contains the tests for https://golang.org/cl/18675
      
      Semi-related change noticed while writing the tests: now that we have
      TLSNextProto in Go 1.6, which consults the TLS
      ConnectionState.NegotiatedProtocol, we have to gurantee that the TLS
      handshake has been done before we look at the ConnectionState. So add
      that check after the DialTLS hook. (we never documented that users
      have to call Handshake, so do it for them, now that it matters)
      
      Updates #13957
      
      Change-Id: I9a70e9d1282fe937ea654d9b1269c984c4e366c0
      Reviewed-on: https://go-review.googlesource.com/18676Reviewed-by: 's avatarAndrew Gerrand <adg@golang.org>
      Run-TryBot: Brad Fitzpatrick <bradfitz@golang.org>
      TryBot-Result: Gobot Gobot <gobot@golang.org>
      91b910b7
    • Keith Randall's avatar
      [dev.ssa] runtime: fix windows build · 594c3aa0
      Keith Randall authored
      Pull the relevant part of https://go-review.googlesource.com/#/c/18304/
      into the SSA branch.  This fixes the windows SSA build.
      
      Change-Id: Iee3834d8e7019cd90307e32029f3d1032ceb46c1
      Reviewed-on: https://go-review.googlesource.com/18673Reviewed-by: 's avatarAustin Clements <austin@google.com>
      594c3aa0
    • Austin Clements's avatar
      runtime: use at least "system" traceback level for runtime tests · 1556c317
      Austin Clements authored
      While the default behavior of eliding runtime frames from tracebacks
      usually makes sense, this is not the case when you're trying to test
      the runtime itself. Fix this by forcing the traceback level to at
      least "system" in the runtime tests.
      
      This will specifically help with debugging issue #13645, which has
      proven remarkably resistant to reproduction outside of the build
      dashboard itself.
      
      Change-Id: I2a8356ba6c3c5badba8bb3330fc527357ec0d296
      Reviewed-on: https://go-review.googlesource.com/18648
      Run-TryBot: Austin Clements <austin@google.com>
      TryBot-Result: Gobot Gobot <gobot@golang.org>
      Reviewed-by: 's avatarAlex Brainman <alex.brainman@gmail.com>
      1556c317
  11. 14 Jan, 2016 6 commits