roachtest: properly fail when uploading binaries fails#41083
Merged
craig[bot] merged 1 commit intocockroachdb:masterfrom Sep 25, 2019
Merged
roachtest: properly fail when uploading binaries fails#41083craig[bot] merged 1 commit intocockroachdb:masterfrom
craig[bot] merged 1 commit intocockroachdb:masterfrom
Conversation
Closes cockroachdb#41016. Closes cockroachdb#40864. Closes cockroachdb#40578. In all of the referenced issues, we were seeing uploading cockroach binaries fail (which should be idempotent). We could see this in the log: ``` 05:11:12 test.go:182: test status: uploading binary 05:11:12 cluster.go:315: > /home/agent/work/.go/src/github.com/cockroachdb/cockroach/bin/roachprod put teamcity-1569301790-07-n4cpu4 /home/agent/work/.go/src/github.com/cockroachdb/cockroach/cockroach.linux-2.6.32-gnu-amd64 ./cockroach teamcity-1569301790-07-n4cpu4: putting (dist) /home/agent/work/.go/src/github.com/cockroachdb/cockroach/cockroach.linux-2.6.32-gnu-amd64 ./cockroach ................ 1: done 2: ~ scp -r -C -o StrictHostKeyChecking=no -i /root/.ssh/id_rsa -i /root/.ssh/google_compute_engine /home/agent/work/.go/src/github.com/cockroachdb/cockroach/cockroach.linux-2.6.32-gnu-amd64 root@35.222.255.152:./cockroach Warning: Permanently added '35.222.255.152' (ECDSA) to the list of known hosts. packet_write_wait: Connection to 35.222.255.152 port 22: Broken pipe lost connection : exit status 1 3: done 4: done I190924 05:11:29.022222 1 cluster_synced.go:1088 put /home/agent/work/.go/src/github.com/cockroachdb/cockroach/cockroach.linux-2.6.32-gnu-amd64 failed ``` The test would then ignore the failure and proceed to get tripped up when starting cockroach: ``` 05:11:34 cluster.go:315: > /home/agent/work/.go/src/github.com/cockroachdb/cockroach/bin/roachprod start --racks=1 --args=--locality-advertise-addr=rack=0@35.222.255.152 teamcity-1569301790-07-n4cpu4:2 teamcity-1569301790-07-n4cpu4: starting 0: exit status 255 ~ ./cockroach version github.com/cockroachdb/cockroach/pkg/cmd/roachprod/install.getCockroachVersion /home/agent/work/.go/src/github.com/cockroachdb/cockroach/pkg/cmd/roachprod/install/cockroach.go:88 github.com/cockroachdb/cockroach/pkg/cmd/roachprod/install.Cockroach.Start.func1 /home/agent/work/.go/src/github.com/cockroachdb/cockroach/pkg/cmd/roachprod/install/cockroach.go:149 github.com/cockroachdb/cockroach/pkg/cmd/roachprod/install.(*SyncedCluster).Parallel.func1.1 /home/agent/work/.go/src/github.com/cockroachdb/cockroach/pkg/cmd/roachprod/install/cluster_synced.go:1535 runtime.goexit /usr/local/go/src/runtime/asm_amd64.s:1337: ``` The problem was that we were ignoring the Put error accidentally, so the tests got very confused. This commit fixes this by properly handling the Put error. This doesn't actually fix the referenced issues entirely, but it gets us a step closer to doing so, so I'm going to use it as an opportunity to close them. Release justification: Testing only. Release note: None
Member
Contributor
|
LGTM
…On Wed, Sep 25, 2019 at 12:31 PM cockroach-teamcity < ***@***.***> wrote:
This change is [image: Reviewable]
<https://reviewable.io/reviews/cockroachdb/cockroach/41083>
—
You are receiving this because your review was requested.
Reply to this email directly, view it on GitHub
<#41083?email_source=notifications&email_token=AAC4C4KEBFTOB54IIIFTTNTQLOG4XA5CNFSM4I2PHAA2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD7SQVDI#issuecomment-535104141>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAC4C4ICBAWEGILUWQO6CJDQLOG4XANCNFSM4I2PHAAQ>
.
|
Contributor
Author
|
bors r+ |
craig bot
pushed a commit
that referenced
this pull request
Sep 25, 2019
41083: roachtest: properly fail when uploading binaries fails r=nvanbenschoten a=nvanbenschoten Closes #41016. Closes #40864. Closes #40578. In all of the referenced issues, we were seeing uploading cockroach binaries fail (which should be idempotent). We could see this in the log: ``` 05:11:12 test.go:182: test status: uploading binary 05:11:12 cluster.go:315: > /home/agent/work/.go/src/github.com/cockroachdb/cockroach/bin/roachprod put teamcity-1569301790-07-n4cpu4 /home/agent/work/.go/src/github.com/cockroachdb/cockroach/cockroach.linux-2.6.32-gnu-amd64 ./cockroach teamcity-1569301790-07-n4cpu4: putting (dist) /home/agent/work/.go/src/github.com/cockroachdb/cockroach/cockroach.linux-2.6.32-gnu-amd64 ./cockroach ................ 1: done 2: ~ scp -r -C -o StrictHostKeyChecking=no -i /root/.ssh/id_rsa -i /root/.ssh/google_compute_engine /home/agent/work/.go/src/github.com/cockroachdb/cockroach/cockroach.linux-2.6.32-gnu-amd64 root@35.222.255.152:./cockroach Warning: Permanently added '35.222.255.152' (ECDSA) to the list of known hosts. packet_write_wait: Connection to 35.222.255.152 port 22: Broken pipe lost connection : exit status 1 3: done 4: done I190924 05:11:29.022222 1 cluster_synced.go:1088 put /home/agent/work/.go/src/github.com/cockroachdb/cockroach/cockroach.linux-2.6.32-gnu-amd64 failed ``` The test would then ignore the failure and proceed to get tripped up when starting cockroach: ``` 05:11:34 cluster.go:315: > /home/agent/work/.go/src/github.com/cockroachdb/cockroach/bin/roachprod start --racks=1 --args=--locality-advertise-addr=rack=0@35.222.255.152 teamcity-1569301790-07-n4cpu4:2 teamcity-1569301790-07-n4cpu4: starting 0: exit status 255 ~ ./cockroach version github.com/cockroachdb/cockroach/pkg/cmd/roachprod/install.getCockroachVersion /home/agent/work/.go/src/github.com/cockroachdb/cockroach/pkg/cmd/roachprod/install/cockroach.go:88 github.com/cockroachdb/cockroach/pkg/cmd/roachprod/install.Cockroach.Start.func1 /home/agent/work/.go/src/github.com/cockroachdb/cockroach/pkg/cmd/roachprod/install/cockroach.go:149 github.com/cockroachdb/cockroach/pkg/cmd/roachprod/install.(*SyncedCluster).Parallel.func1.1 /home/agent/work/.go/src/github.com/cockroachdb/cockroach/pkg/cmd/roachprod/install/cluster_synced.go:1535 runtime.goexit /usr/local/go/src/runtime/asm_amd64.s:1337: ``` The problem was that we were ignoring the Put error accidentally, so the tests got very confused. This commit fixes this by properly handling the Put error. This doesn't actually fix the referenced issues entirely, but it gets us a step closer to doing so, so I'm going to use it as an opportunity to close them. Release justification: Testing only. Release note: None Co-authored-by: Nathan VanBenschoten <nvanbenschoten@gmail.com>
Contributor
Build succeeded |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Closes #41016.
Closes #40864.
Closes #40578.
In all of the referenced issues, we were seeing uploading cockroach
binaries fail (which should be idempotent). We could see this in the
log:
The test would then ignore the failure and proceed to get tripped up
when starting cockroach:
The problem was that we were ignoring the Put error accidentally, so the
tests got very confused. This commit fixes this by properly handling the
Put error. This doesn't actually fix the referenced issues entirely, but
it gets us a step closer to doing so, so I'm going to use it as an
opportunity to close them.
Release justification: Testing only.
Release note: None