As of https://go.dev/cl/564197 (for #65064), all 4 perf builders are failing due to cockroachdb errors.

e.g., https://ci.chromium.org/ui/p/golang/builders/ci/gotip-linux-arm64_c4ah72-perf_vs_release/b8716897839307984241/overview

[sweet] error: run benchmark cockroachdb for config experiment: exit status 1
Tail of log (/home/swarming/.swarming/w/ir/x/t/go-sweet2521400662/results/cockroachdb/experiment.log):
external I/O path:   /home/swarming/.swarming/w/ir/x/t/go-sweet2521400662/work/cockroachdb/experiment/tmp/roach-node/extern
store[0]:            path=/home/swarming/.swarming/w/ir/x/t/go-sweet2521400662/work/cockroachdb/experiment/tmp/roach-node
storage engine:      pebble
clusterID:           2d2165f0-849e-4d6d-952c-6a7068f2b375
status:              initialized new cluster
nodeID:              1

=== Instance "roach-node" original stderr ===
I250422 11:36:15.334032 1 util/log/file_sync_buffer.go:242 ⋮ [config]   file created at: 2025/04/22 11:36:15
I250422 11:36:15.334043 1 util/log/file_sync_buffer.go:242 ⋮ [config]   running on machine: ‹golang-ciw-c4a-72-linux-arm64-bookworm-us-east4-a-0-149a›
I250422 11:36:15.334050 1 util/log/file_sync_buffer.go:242 ⋮ [config]   binary: CockroachDB CCL v24.2.0-alpha.00000000-dev (linux arm64, built , devel 352dd2d932c1c1c6dbc3e112fcdfface07d4fffb)
I250422 11:36:15.334056 1 util/log/file_sync_buffer.go:242 ⋮ [config]   arguments: [‹/home/swarming/.swarming/w/ir/x/t/go-sweet2521400662/work/cockroachdb/experiment/bin/cockroach› ‹start-single-node› ‹--insecure› ‹--listen-addr› ‹localhost:26257› ‹--http-addr› ‹localhost:26258› ‹--cache› ‹0.25› ‹--store› ‹/home/swarming/.swarming/w/ir/x/t/go-sweet2521400662/work/cockroachdb/experiment/tmp/roach-node› ‹--log-dir› ‹/home/swarming/.swarming/w/ir/x/t/go-sweet2521400662/work/cockroachdb/experiment/tmp/roach-node-log›]
I250422 11:36:15.334072 1 util/log/file_sync_buffer.go:242 ⋮ [config]   log format (utf8=✓): crdb-v2
I250422 11:36:15.334074 1 util/log/file_sync_buffer.go:242 ⋮ [config]   line format: [IWEF]yymmdd hh:mm:ss.uuuuuu goid [chan@]file:line redactionmark \[tags\] [counter] msg
I250422 11:36:15.333849 1 util/log/flags.go:222  [-] 1  stderr capture started

error: workload failed to become available within timeout: error: signal: killed: output:
I250422 11:36:40.865692 1 workload/cli/run.go:640  [-] 1  random seed: 6233835059417767123
I250422 11:36:40.865770 1 workload/cli/run.go:432  [-] 2  creating load generator...

At the moment, this CL is the most recent run of these builders, so more data will be useful to see if this is consistent. But given that all builders failed, it seems less likely to be a flake.

Comment From: gabyhelp

Related Issues

(Emoji vote if this was helpful or unhelpful; more detailed feedback welcome in this discussion.)

Comment From: gopherbot

Change https://go.dev/cl/667336 mentions this issue: Revert "runtime: only poll network from one P at a time in findRunnable"

Comment From: gopherbot

Change https://go.dev/cl/668735 mentions this issue: sweet/harnesses: update the version of Cockroachdb benchmarked

Comment From: gopherbot

Change https://go.dev/cl/670416 mentions this issue: sweet/harnesses: update the version of CockroachDB benchmarked

Comment From: cagedmantis

While we were working to address Issue #65064, we submitted CL 564197. Once that CL was submitted, the perf builders began failing. The failures were due to CockroachDB benchmark failures. The failures were timeouts in the tests. The failures were due to CockroachDB using a internal copy/clone of schedt which became out of sync with the Go runtime. CockroachDB has transitioned from using an internal copy/clone of schedt. When we run the benchmark against the tip version of CockroachDB it fails because of a another issue https://github.com/cockroachdb/cockroach/issues/124021. We should update the version that we test against and attempt to exclude the failing benchmark BenchmarkSQLCatchVectorizedRuntimeError.

Comment From: cagedmantis

Following up on the previous message. We should update the version that we test against and attempt to mitigate the effects of the root cause of the error condition found in https://github.com/cockroachdb/cockroach/issues/124021. I will mail a CL updating the version of CockroachDB we benchmark against and then send a follow-up CL which retries failing benchmarks. The error we are experiencing i logged as:

/home/swarming/.swarming/w/ir/tmp/go-sweet978346786/work/cockroachdb/baseline/bin/cockroach workload init kv postgres://root@localhost:26257?sslmode=disable
/home/swarming/.swarming/w/ir/tmp/go-sweet978346786/work/cockroachdb/baseline/bin/cockroach workload run kv --read-percent=50 --min-block-bytes=1024 --max-block-bytes=1024 --concurrency=10000 --max-rate=30000 --scatter --splits=5 --ramp=0s --duration=500ms postgres://root@localhost:26257?sslmode=disable
/home/swarming/.swarming/w/ir/tmp/go-sweet978346786/work/cockroachdb/baseline/bin/cockroach workload run kv --read-percent=50 --min-block-bytes=1024 --max-block-bytes=1024 --concurrency=10000 --max-rate=30000 --scatter --splits=5 --ramp=15s --duration=1m postgres://root@localhost:26257?sslmode=disable
exit status 1

I250507 20:06:46.930810 1 workload/cli/run.go:649  [-] 1  random seed: -6780016327593225364
I250507 20:06:48.349557 1 workload/cli/run.go:649  [-] 1  random seed: -3211894271932946231
I250507 20:06:48.349665 1 workload/cli/run.go:460  [-] 2  creating load generator...
I250507 20:06:48.780665 1 workload/cli/run.go:499  [-] 3  creating load generator... done (took 430.998554ms)
W250507 20:06:48.783756 49098 workload/pgx_helpers.go:235  [-] 4  error preparing statement. name=kv-2 sql=SELECT k, v FROM kv AS OF SYSTEM TIME follower_read_timestamp() WHERE k IN ($1) ERROR: database "kv" does not exist (SQLSTATE 3D000)
W250507 20:06:48.784155 49099 workload/pgx_helpers.go:235  [-] 5  error preparing statement. name=kv-2 sql=SELECT k, v FROM kv AS OF SYSTEM TIME follower_read_timestamp() WHERE k IN ($1) ERROR: database "kv" does not exist (SQLSTATE 3D000)
W250507 20:06:48.785971 49100 workload/pgx_helpers.go:235  [-] 7  error preparing statement. name=kv-2 sql=SELECT k, v FROM kv AS OF SYSTEM TIME follower_read_timestamp() WHERE k IN ($1) ERROR: database "kv" does not exist (SQLSTATE 3D000)
W250507 20:06:48.785957 49098 workload/pgx_helpers.go:235  [-] 6  error preparing statement. name=kv-2 sql=SELECT k, v FROM kv AS OF SYSTEM TIME follower_read_timestamp() WHERE k IN ($1) ERROR: database "kv" does not exist (SQLSTATE 3D000)
W250507 20:06:51.268981 51800 workload/pgx_helpers.go:235  [-] 9158  error preparing statement. name=kv-2 sql=SELECT k, v FROM kv AS OF SYSTEM TIME follower_read_timestamp() WHERE k IN ($1) ERROR: relation "kv" does not exist (SQLSTATE 42P01)
W250507 20:06:51.269238 50710 workload/pgx_helpers.go:235  [-] 9159  error preparing statement. name=kv-2 sql=SELECT k, v FROM kv AS OF SYSTEM TIME follower_read_timestamp() WHERE k IN ($1) ERROR: relation "kv" does not exist (SQLSTATE 42P01)
W250507 20:06:51.269225 50648 workload/pgx_helpers.go:235  [-] 9161  error preparing statement. name=kv-2 sql=SELECT k, v FROM kv AS OF SYSTEM TIME follower_read_timestamp() WHERE k IN ($1) ERROR: database "kv" does not exist (SQLSTATE 3D000)
W250507 20:06:51.269239 51320 workload/pgx_helpers.go:235  [-] 9160  error preparing statement. name=kv-2 sql=SELECT k, v FROM kv AS OF SYSTEM TIME follower_read_timestamp() WHERE k IN ($1) ERROR: database "kv" does not exist (SQLSTATE 3D000)
...
W250507 20:06:51.269378 51156 workload/pgx_helpers.go:235  [-] 9162  error preparing statement. name=kv-2 sql=SELECT k, v FROM kv AS OF SYSTEM TIME follower_read_timestamp() WHERE k IN ($1) ERROR: relation "kv" does not exist (SQLSTATE 42P01)
W250507 20:06:51.269472 52025 workload/pgx_helpers.go:235  [-] 9163  error preparing statement. name=kv-2 sql=SELECT k, v FROM kv AS OF SYSTEM TIME follower_read_timestamp() WHERE k IN ($1) ERROR: relation "kv" does not exist (SQLSTATE 42P01)
...
W250507 20:06:51.269653 51631 workload/pgx_helpers.go:235  [-] 9164  error preparing statement. name=kv-2 sql=SELECT k, v FROM kv AS OF SYSTEM TIME follower_read_timestamp() WHERE k IN ($1) ERROR: database "kv" does not exist (SQLSTATE 3D000)
W250507 20:06:51.269804 50887 workload/pgx_helpers.go:235  [-] 9165  error preparing statement. name=kv-2 sql=SELECT k, v FROM kv AS OF SYSTEM TIME follower_read_timestamp() WHERE k IN ($1) ERROR: database "kv" does not exist (SQLSTATE 3D000)
W250507 20:06:51.270143 50621 workload/pgx_helpers.go:235  [-] 9166  error preparing statement. name=kv-2 sql=SELECT k, v FROM kv AS OF SYSTEM TIME follower_read_timestamp() WHERE k IN ($1) ERROR: database "kv" does not exist (SQLSTATE 3D000)
W250507 20:06:51.894682 50869 workload/pgx_helpers.go:235  [-] 10405  error preparing statement. name=kv-2 sql=SELECT k, v FROM kv AS OF SYSTEM TIME follower_read_timestamp() WHERE k IN ($1) ERROR: database "kv" does not exist (SQLSTATE 3D000)
W250507 20:06:51.894684 50754 workload/pgx_helpers.go:235  [-] 10406  error preparing statement. name=kv-2 sql=SELECT k, v FROM kv AS OF SYSTEM TIME follower_read_timestamp() WHERE k IN ($1) ERROR: database "kv" does not exist (SQLSTATE 3D000)
E250507 20:07:02.748440 1 workload/cli/run.go:583  [-] 10407  workload run error: failed to connect to `host=localhost user=root database=kv`: dial error (dial tcp [::1]:26257: connect: cannot assign requested address)
E250507 20:07:02.748440 1 workload/cli/run.go:583  [-] 10407 +(1) failed to connect to `host=localhost user=root database=kv`: dial error (dial tcp [::1]:26257: connect: cannot assign requested address)
E250507 20:07:02.748440 1 workload/cli/run.go:583  [-] 10407 +Wraps: (2) dial tcp [::1]:26257
E250507 20:07:02.748440 1 workload/cli/run.go:583  [-] 10407 +Wraps: (3) connect
E250507 20:07:02.748440 1 workload/cli/run.go:583  [-] 10407 +Wraps: (4) cannot assign requested address
E250507 20:07:02.748440 1 workload/cli/run.go:583  [-] 10407 +Error types: (1) *pgconn.ConnectError (2) *net.OpError (3) *os.SyscallError (4) syscall.Errno
Error: failed to connect to `host=localhost user=root database=kv`: dial error (dial tcp [::1]:26257: connect: cannot assign requested address)

Comment From: gopherbot

Change https://go.dev/cl/679755 mentions this issue: sweet: upgrade cockroachdb to v25.2.0 and re-enable

Comment From: gopherbot

Change https://go.dev/cl/681595 mentions this issue: sweet/benchmarks/cockroachdb: reduce benchmark concurrency