1. 16 Feb, 2016 5 commits
  2. 13 Feb, 2016 2 commits
  3. 12 Feb, 2016 4 commits
  4. 11 Feb, 2016 1 commit
  5. 10 Feb, 2016 3 commits
  6. 09 Feb, 2016 5 commits
  7. 08 Feb, 2016 3 commits
  8. 07 Feb, 2016 1 commit
  9. 06 Feb, 2016 1 commit
    • Ian Lance Taylor's avatar
      net/http: deflake TestCloseNotifierPipelined · 54b4b946
      Ian Lance Taylor authored
      The test sends two HTTP/1.1 pipelined requests.  The first is
      completedly by the second, and as such triggers an immediate call to the
      CloseNotify channel.  The second calls the CloseNotify channel after the
      overall connection is closed.
      
      The test was passing fine on gc because the code would enter the select
      loop before running the handler, so the send on gotReq would always be
      seen first.  On gccgo the code would sometimes enter the select loop
      after the handler had already finished, meaning that the select could
      choose between gotReq and sawClose.  If it picked sawClose, it would
      never close the overall connection, and the httptest server would hang.
      The same hang could be induced with gc by adding a time.Sleep
      immediately before the select loop.
      
      Deflake the test by 1) don't close the overall connection until both
      requests have been seen; 2) don't exit the loop until both closes have
      been seen.
      
      Fixes #14231.
      
      Change-Id: I9d20c309125422ce60ac545f78bcfa337aec1c7d
      Reviewed-on: https://go-review.googlesource.com/19281Reviewed-by: default avatarBrad Fitzpatrick <bradfitz@golang.org>
      Run-TryBot: Ian Lance Taylor <iant@golang.org>
      TryBot-Result: Gobot Gobot <gobot@golang.org>
      54b4b946
  10. 05 Feb, 2016 3 commits
  11. 04 Feb, 2016 4 commits
  12. 03 Feb, 2016 5 commits
  13. 02 Feb, 2016 3 commits