1. 19 Feb, 2016 20 commits
  2. 18 Feb, 2016 10 commits
  3. 17 Feb, 2016 5 commits
  4. 16 Feb, 2016 5 commits
    • Ian Lance Taylor's avatar
      cmd/go: avoid race on test environment · aa22c42d
      Ian Lance Taylor authored
      Fixes #14337.
      
      Change-Id: I58aef7e08d936b0712da577dd1ce5c9ed5d8bfd2
      Reviewed-on: https://go-review.googlesource.com/19513Reviewed-by: default avatarRuss Cox <rsc@golang.org>
      aa22c42d
    • Austin Clements's avatar
      runtime: fix deadlock in TestCrashDumpsAllThreads · 7c22af83
      Austin Clements authored
      TestCrashDumpsAllThreads carefully sets the number of Ps to one
      greater than the number of non-preemptible loops it starts so that the
      main goroutine can continue to run (necessary because of #10958).
      However, if GC starts, it can take over that one spare P and lock up
      the system while waiting for the non-preemptible loops, causing the
      test to eventually time out. This deadlock is easily reproducible if
      you run the runtime test with GOGC=1.
      
      Fix this by forcing GOGC=off when running this test.
      
      Change-Id: Ifb22da5ce33f9a61700a326ea92fcf4b049721d1
      Reviewed-on: https://go-review.googlesource.com/19516
      Run-TryBot: Austin Clements <austin@google.com>
      TryBot-Result: Gobot Gobot <gobot@golang.org>
      Reviewed-by: default avatarRuss Cox <rsc@golang.org>
      7c22af83
    • Russ Cox's avatar
      cmd/compile: print struct tags in var decl in inlined func body · feb2a5d6
      Russ Cox authored
      This bug was introduced in golang.org/cl/18217,
      while trying to fix #13777.
      
      Originally I wanted to just disable inlining for the case
      being handled incorrectly, but it's fairly difficult to detect
      and much easier just to fix. Since the case being handled
      incorrectly was inlined correctly in Go 1.5, not inlining it
      would also be somewhat of a regression.
      So just fix it.
      
      Test case copied from Ian's CL 19520.
      
      The mistake to worry about in this CL would be relaxing
      the condition too much (we now print the note more often
      than we did yesterday). To confirm that we'd catch this mistake,
      I checked that changing (!fmtbody || !t.Funarg) to (true) does
      cause fixedbugs/issue13777.go to fail. And putting it back
      to what is written in this CL makes that test pass again
      as well as the new fixedbugs/issue14331.go.
      So I believe that the new condition is correct for both constraints.
      
      Fixes #14331.
      
      Change-Id: I91f75a4d5d07c53af5caea1855c780d9874b8df6
      Reviewed-on: https://go-review.googlesource.com/19514
      Run-TryBot: Russ Cox <rsc@golang.org>
      TryBot-Result: Gobot Gobot <gobot@golang.org>
      Reviewed-by: default avatarIan Lance Taylor <iant@golang.org>
      feb2a5d6
    • Alex Brainman's avatar
      net: make TestInterfaceAddrsWithNetsh more robust · e136cac4
      Alex Brainman authored
      TestInterfaceAddrsWithNetsh invokes Windows netsh command passing
      it a particular interface name. This approach somehow does not work
      on some computers (see issue for details). Change that to call netsh
      without specifying any interface name. This provides output for all
      interfaces available. So we can achieve same goal parsing this output.
      Also makes test faster because we only need to invoke netsh once.
      
      Fixes #14130.
      
      Change-Id: I7911692ca64e372af1e1f9d6acb718c67071de67
      Reviewed-on: https://go-review.googlesource.com/19441Reviewed-by: default avatarVolker Dobler <dr.volker.dobler@gmail.com>
      Run-TryBot: Russ Cox <rsc@golang.org>
      TryBot-Result: Gobot Gobot <gobot@golang.org>
      Reviewed-by: default avatarRuss Cox <rsc@golang.org>
      e136cac4
    • Austin Clements's avatar
      runtime: show panics in traceback · 0c02bc00
      Austin Clements authored
      We used to include panic calls in tracebacks; however, when
      runtime.panic was renamed to runtime.gopanic in the conversion of the
      runtime to Go, we missed the special case in showframe that includes
      panic calls even though they're in package runtime.
      
      Fix the function name check in showframe (and, while we're here, fix
      the other check for "runtime.panic" in runtime/pprof). Since the
      "runtime.gopanic" name doesn't match what users call panic and hence
      isn't very user-friendly, make traceback rewrite it to just "panic".
      
      Updates #5832, #13857. Fixes #14315.
      
      Change-Id: I8059621b41ec043e63d5cfb4cbee479f47f64973
      Reviewed-on: https://go-review.googlesource.com/19492
      Run-TryBot: Austin Clements <austin@google.com>
      TryBot-Result: Gobot Gobot <gobot@golang.org>
      Reviewed-by: default avatarRuss Cox <rsc@golang.org>
      0c02bc00