Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

all: golang.org/x repos need to stay green #11811

Open
rsc opened this issue Jul 21, 2015 · 75 comments
Open

all: golang.org/x repos need to stay green #11811

rsc opened this issue Jul 21, 2015 · 75 comments

Comments

@rsc
Copy link
Contributor

@rsc rsc commented Jul 21, 2015

We need to get the subrepos green consistently for 1.5 and moving forward.

@rsc rsc added this to the Go1.5 milestone Jul 21, 2015
gopherbot pushed a commit to golang/tools that referenced this issue Jul 29, 2015
Update golang/go#11811

Change-Id: I3d875acf58a015fa4cae16473a118ac8196b9b44
Reviewed-on: https://go-review.googlesource.com/12789
Reviewed-by: Andrew Gerrand <adg@golang.org>
@gopherbot
Copy link

@gopherbot gopherbot commented Jul 29, 2015

CL https://golang.org/cl/12788 mentions this issue.

@gopherbot
Copy link

@gopherbot gopherbot commented Jul 29, 2015

CL https://golang.org/cl/12830 mentions this issue.

gopherbot pushed a commit to golang/tools that referenced this issue Jul 29, 2015
Update golang/go#11811

Change-Id: I1f8977cf8eed84936c7c2b568f87abe88f5723f9
Reviewed-on: https://go-review.googlesource.com/12788
Reviewed-by: Brad Fitzpatrick <bradfitz@golang.org>
@gopherbot
Copy link

@gopherbot gopherbot commented Jul 29, 2015

CL https://golang.org/cl/12832 mentions this issue.

@gopherbot
Copy link

@gopherbot gopherbot commented Jul 29, 2015

CL https://golang.org/cl/12765 mentions this issue.

alandonovan added a commit to golang/tools that referenced this issue Jul 29, 2015
Some standard library dependencies have changed (packages and files).
Both ExampleConfig_CreateFromFiles and ExampleConfig_Import Output
needs to be adjusted. Do that.

Update golang/go#11811

Change-Id: I523f2adc1aa46f0932a71ccb23dd7c5a6b07fb27
Reviewed-on: https://go-review.googlesource.com/12832
Reviewed-by: Alan Donovan <adonovan@google.com>
gopherbot pushed a commit to golang/tools that referenced this issue Jul 30, 2015
Update golang/go#11811

Change-Id: Ic5f1ea87c88d563b6e0ef2d44042e28a9ea03a03
Reviewed-on: https://go-review.googlesource.com/12830
Reviewed-by: Robert Griesemer <gri@golang.org>
@gopherbot
Copy link

@gopherbot gopherbot commented Jul 30, 2015

CL https://golang.org/cl/12838 mentions this issue.

@gopherbot
Copy link

@gopherbot gopherbot commented Jul 31, 2015

CL https://golang.org/cl/13008 mentions this issue.

griesemer added a commit to golang/tools that referenced this issue Jul 31, 2015
For golang/go#11811.

Change-Id: I130f9608840177cfb7fb9fae30765fcb5aa77411
Reviewed-on: https://go-review.googlesource.com/13008
Reviewed-by: Russ Cox <rsc@golang.org>
@gopherbot
Copy link

@gopherbot gopherbot commented Jul 31, 2015

CL https://golang.org/cl/13032 mentions this issue.

@gopherbot
Copy link

@gopherbot gopherbot commented Jul 31, 2015

CL https://golang.org/cl/13009 mentions this issue.

griesemer added a commit to golang/tools that referenced this issue Jul 31, 2015
This should help on slower machines.

For golang/go#11811.

Change-Id: Ibb5d5bf0f6cedcda6437ef0ee3fc1f4ba89dab90
Reviewed-on: https://go-review.googlesource.com/13009
Reviewed-by: Ian Lance Taylor <iant@golang.org>
griesemer added a commit to golang/tools that referenced this issue Jul 31, 2015
The output of ExampleConfig_CreateFromFiles and ExampleConfig_Import
are different for Windows that for other platforms: They contain
internal/syscall/windows packages and unicode/utf16 not present in
the output for other platforms.

For golang/go#11811.

Change-Id: Id391fbeec8123616da86cb68fc3cefcd513b2493
Reviewed-on: https://go-review.googlesource.com/13032
Reviewed-by: Ian Lance Taylor <iant@golang.org>
griesemer added a commit to golang/tools that referenced this issue Jul 31, 2015
Attempt to make build work on Plan 9.

For golang/go#11811.

Change-Id: I37a5eaef441262342994a8f77c86aa5e120deea7
Reviewed-on: https://go-review.googlesource.com/13033
Reviewed-by: Ian Lance Taylor <iant@golang.org>
griesemer added a commit to golang/tools that referenced this issue Jul 31, 2015
See golang/go#11975.
For golang/go#11811.

Change-Id: I56ee20cd798bf963afdf3c81c4745f07850f6dcc
Reviewed-on: https://go-review.googlesource.com/13034
Reviewed-by: Ian Lance Taylor <iant@golang.org>
@gopherbot
Copy link

@gopherbot gopherbot commented Aug 1, 2015

CL https://golang.org/cl/12916 mentions this issue.

gopherbot pushed a commit to golang/crypto that referenced this issue Aug 2, 2015
Update golang/go#11811

The increased default concurrency in Go 1.5 showed up a test flake in
the TestHostKeyCert test. Under load, when the client provided incorrect
data, both sides would race to tear down the connection, which would often
lead to the server side, running in its own goroutine to see an unexpected
EOF or connection reset.

Fix this flake (and the incorrect use of t.Fatalf) by passing the error back
to the main goroutine for inspection. This also lets us ignore the expected
error in the unsuccessful path

Change-Id: I5a95c6d240479e9d537f34177e5ca8023b1b08e9
Reviewed-on: https://go-review.googlesource.com/12916
Reviewed-by: Brad Fitzpatrick <bradfitz@golang.org>
bradfitz added a commit to golang/exp that referenced this issue Aug 4, 2015
…empty

The builders don't have X. (notably Darwin)

Perhaps the Linux ones should. Or some should. Please file a separate bug for that.

Somebody else might want to upstream this fix to BurntSushi.

Updates golang/go#11811

Change-Id: I6d270a83fc59a3923723b5bfbd0b92057a484a1c
Reviewed-on: https://go-review.googlesource.com/12765
Reviewed-by: Nigel Tao <nigeltao@golang.org>
@gopherbot
Copy link

@gopherbot gopherbot commented Aug 5, 2015

CL https://golang.org/cl/13252 mentions this issue.

rsc added a commit to golang/text that referenced this issue Aug 5, 2015
For golang/go#11811.
Fixes golang/go#11927.

Change-Id: Ie60c687ba93aaeb6c164413289f474be63e0224f
Reviewed-on: https://go-review.googlesource.com/13252
Reviewed-by: Robert Griesemer <gri@golang.org>
@gopherbot
Copy link

@gopherbot gopherbot commented Aug 6, 2015

CL https://golang.org/cl/13268 mentions this issue.

griesemer added a commit to golang/tools that referenced this issue Aug 6, 2015
For golang/go#11811.

Change-Id: Icf16a2d47fcf2fe0d79dd825ccb851a3d63a660f
Reviewed-on: https://go-review.googlesource.com/13268
Reviewed-by: Rob Pike <r@golang.org>
Reviewed-by: David Crawshaw <crawshaw@golang.org>
@gopherbot
Copy link

@gopherbot gopherbot commented Jan 22, 2021

Change https://golang.org/cl/285712 mentions this issue: execabs: disable tests on ios and js/wasm

gopherbot pushed a commit to golang/sys that referenced this issue Jan 23, 2021
TestCommand and TestLookPath fail on the js/wasm builder and likely
fail on ios as well.

Like the tests in internal/execabs, skip them for these platforms.

This fixes the js/wasm builder after CL 284753.

For golang/go#11811

Change-Id: I1038128bd4c7bd410ac1357dedda5e3eef5c7bbb
Reviewed-on: https://go-review.googlesource.com/c/sys/+/285712
Trust: Tobias Klauser <tobias.klauser@gmail.com>
Run-TryBot: Tobias Klauser <tobias.klauser@gmail.com>
TryBot-Result: Go Bot <gobot@golang.org>
Reviewed-by: Ian Lance Taylor <iant@golang.org>
@toothrot
Copy link
Contributor

@toothrot toothrot commented Jan 27, 2021

Creating release branches with updated naming scheme from #36882 for Go 1.16:

# golang.org/x/arch v0.0.0-20201008161808-52c3e6f60cff
# golang.org/x/crypto v0.0.0-20201016220609-9e8e0b390897
# golang.org/x/mod v0.4.1
# golang.org/x/net v0.0.0-20201209123823-ac852fbbde11
# golang.org/x/sys v0.0.0-20201204225414-ed752295db88
# golang.org/x/text v0.3.4
# golang.org/x/tools v0.0.0-20210107193943-4ed967dd8eff
# golang.org/x/xerrors v0.0.0-20200804184101-5ec99f83aff1
@gopherbot
Copy link

@gopherbot gopherbot commented Apr 28, 2021

Change https://golang.org/cl/314598 mentions this issue: [internal-branch.go1.16-vendor] ipv6: skip known-failing tests on openbsd-{arm,arm64,mips64}-jsing builders

@gopherbot
Copy link

@gopherbot gopherbot commented Apr 28, 2021

Change https://golang.org/cl/314599 mentions this issue: [release-branch.go1.15] ipv6: skip known-failing tests on openbsd-{arm,arm64,mips64}-jsing builders

@gopherbot
Copy link

@gopherbot gopherbot commented Apr 28, 2021

Change https://golang.org/cl/314749 mentions this issue: [internal-branch.go1.16-vendor] ipv6: skip known-failing tests on OpenBSD 6.8 builders

@gopherbot
Copy link

@gopherbot gopherbot commented Apr 28, 2021

Change https://golang.org/cl/314750 mentions this issue: [release-branch.go1.15] ipv6: skip known-failing tests on OpenBSD 6.8 builders

@gopherbot
Copy link

@gopherbot gopherbot commented Apr 28, 2021

Change https://golang.org/cl/314751 mentions this issue: [release-branch.go1.15-bundle] ipv6: skip known-failing tests on OpenBSD 6.8 builders

gopherbot pushed a commit to golang/net that referenced this issue Apr 28, 2021
…nBSD 6.8 builders

These tests are known to be failing on OpenBSD 6.8 and need
investigation. The OpenBSD 6.8 builders are default TryBots
now, so skip them to prevent people working on other packages
from constantly getting a failure.

Issue 42064 remains open to do the work of determining if the
ipv6 package needs to be fixed, or if OpenBSD 6.8 has a problem
and the test can be permanently skipped as unsupported.

For golang/go#11811.
Updates golang/go#42064.
Updates golang/go#35712.

Change-Id: I59883384e4dbce679cb1a4e8e2c3f0fa7983010b
Reviewed-on: https://go-review.googlesource.com/c/net/+/280052
Run-TryBot: Dmitri Shuralyov <dmitshur@golang.org>
TryBot-Result: Go Bot <gobot@golang.org>
Reviewed-by: Alexander Rakoczy <alex@golang.org>
Trust: Dmitri Shuralyov <dmitshur@golang.org>
(cherry picked from commit 6772e93)
Reviewed-on: https://go-review.googlesource.com/c/net/+/314749
Trust: Katie Hockman <katie@golang.org>
Run-TryBot: Katie Hockman <katie@golang.org>
Reviewed-by: Katie Hockman <katie@golang.org>
gopherbot pushed a commit to golang/net that referenced this issue Apr 28, 2021
…BSD 6.8 builders

These tests are known to be failing on OpenBSD 6.8 and need
investigation. The OpenBSD 6.8 builders are default TryBots
now, so skip them to prevent people working on other packages
from constantly getting a failure.

Issue 42064 remains open to do the work of determining if the
ipv6 package needs to be fixed, or if OpenBSD 6.8 has a problem
and the test can be permanently skipped as unsupported.

For golang/go#11811.
Updates golang/go#42064.
Updates golang/go#35712.

Change-Id: I59883384e4dbce679cb1a4e8e2c3f0fa7983010b
Reviewed-on: https://go-review.googlesource.com/c/net/+/280052
Run-TryBot: Dmitri Shuralyov <dmitshur@golang.org>
TryBot-Result: Go Bot <gobot@golang.org>
Reviewed-by: Alexander Rakoczy <alex@golang.org>
Trust: Dmitri Shuralyov <dmitshur@golang.org>
(cherry picked from commit 6772e93)
Reviewed-on: https://go-review.googlesource.com/c/net/+/314751
Trust: Katie Hockman <katie@golang.org>
Run-TryBot: Katie Hockman <katie@golang.org>
Reviewed-by: Katie Hockman <katie@golang.org>
gopherbot pushed a commit to golang/net that referenced this issue Apr 28, 2021
… builders

These tests are known to be failing on OpenBSD 6.8 and need
investigation. The OpenBSD 6.8 builders are default TryBots
now, so skip them to prevent people working on other packages
from constantly getting a failure.

Issue 42064 remains open to do the work of determining if the
ipv6 package needs to be fixed, or if OpenBSD 6.8 has a problem
and the test can be permanently skipped as unsupported.

For golang/go#11811.
Updates golang/go#42064.
Updates golang/go#35712.

Change-Id: I59883384e4dbce679cb1a4e8e2c3f0fa7983010b
Reviewed-on: https://go-review.googlesource.com/c/net/+/280052
Run-TryBot: Dmitri Shuralyov <dmitshur@golang.org>
TryBot-Result: Go Bot <gobot@golang.org>
Reviewed-by: Alexander Rakoczy <alex@golang.org>
Trust: Dmitri Shuralyov <dmitshur@golang.org>
(cherry picked from commit 6772e93)
Reviewed-on: https://go-review.googlesource.com/c/net/+/314750
Trust: Katie Hockman <katie@golang.org>
Reviewed-by: Katie Hockman <katie@golang.org>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet