You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
# Don't forget to check out a clean suitable branch and experiment with the
# stress invocation until the desired results present themselves. For example,
# using stress instead of stressrace and passing the '-p' stressflag which
# controls concurrency.
./scripts/gceworker.sh start && ./scripts/gceworker.sh mosh
cd ~/go/src/github.com/cockroachdb/cockroach && \
make stressrace TESTS=election-after-restart PKG=roachtest TESTTIMEOUT=5m STRESSFLAGS='-maxtime 20m -timeout 10m' 2>&1 | tee /tmp/stress.log
The test failed on release-2.1:
test.go:611,election.go:67: Error: cannot dial server.
Is the server running?
If the server is running, check --host client-side and --advertise server-side.
read tcp 127.0.0.1:43156->127.0.0.1:26257: i/o timeout
Failed running "sql"
Error: exit status 1
/home/agent/work/.go/bin/roachprod run teamcity-974325-election-after-restart:1 -- ./cockroach sql --insecure -e "
SET TRACING = on;
SELECT * FROM test.kv;
SET TRACING = off;
SHOW TRACE FOR SESSION;
": exit status 1
The text was updated successfully, but these errors were encountered:
It's possible the default of 5s is simply too tight, but as an easy
indication for that we can see what total duration the test takes
assuming it gets plenty of time to connect.
Closescockroachdb#31615.
Release note: None
31723: roachtest: use high connect timeout in election test r=petermattis a=tschottdorf
It's possible the default of 5s is simply too tight, but as an easy
indication for that we can see what total duration the test takes
assuming it gets plenty of time to connect.
Closes#31615.
Release note: None
Co-authored-by: Tobias Schottdorf <[email protected]>
SHA: https://github.com/cockroachdb/cockroach/commits/e6348bb4abbfd117424c382ce5ab42e8abbe88f0
Parameters:
To repro, try:
Failed test: https://teamcity.cockroachdb.com/viewLog.html?buildId=974325&tab=buildLog
The text was updated successfully, but these errors were encountered: