sqlitelogictest: 2-hour time limit isn't sufficient

[cockroach-teamcity]

pkg/sql/sqlitelogictest/tests/local/local_test.TestSqlLiteLogic_testindexview1000slt_good_0_test failed with artifacts on release-22.2.0 @ 58ba620ed525d6e5cf6f509c8a6b9fef75e0f35e:

Slow failing tests:
TestSqlLiteLogic_testindexview1000slt_good_0_test - 11.84s

Slow passing tests:
TestSqlLiteLogic_testindexorderby1000slt_good_0_test - 4568.41s
TestSqlLiteLogic_testindexorderby_nosort1000slt_good_0_test - 1878.13s
TestSqlLiteLogic_testindexdelete100slt_good_2_test - 226.56s
TestSqlLiteLogic_testindexin1000slt_good_0_test - 171.59s
TestSqlLiteLogic_testindexbetween100slt_good_3_test - 115.01s
TestSqlLiteLogic_testindexcommute10slt_good_20_test - 48.15s
TestSqlLiteLogic_testindexcommute100slt_good_7_test - 43.77s
TestSqlLiteLogic_testindexorderby10slt_good_21_test - 43.28s
TestSqlLiteLogic_testindexcommute10slt_good_4_test - 42.49s
TestSqlLiteLogic_testindexorderby_nosort10slt_good_22_test - 23.37s
TestSqlLiteLogic_testindexorderby_nosort10slt_good_37_test - 22.40s

Help

See also: How To Investigate a Go Test Failure (internal)

/cc @cockroachdb/sql-queries

This test on roachdash | Improve this report!

Jira issue: CRDB-20448

[DrewKimball]

Looks like we can still time out on the 2-hour time limit.

No pass/skip/fail event found for test
=== RUN   TestSqlLiteLogic_testindexview1000slt_good_0_test
    test_log_scope.go:161: test logs captured to: /artifacts/tmp/_tmp/a73952b60ff0ae2ffcb12ae85ca66813/logTestSqlLiteLogic_testindexview1000slt_good_0_test1969041055
    test_log_scope.go:79: use -show-logs to present logs inline
[09:18:05] setting distsql_workmem='48549B';
[09:18:05] rng seed: 2643940298289358370
[09:18:07] --- progress: /home/roach/.cache/bazel/_bazel_roach/c5a4e7d36696d9cd970af2045211a7df/sandbox/processwrapper-sandbox/3669/execroot/com_github_cockroachdb_cockroach/bazel-out/k8-fastbuild/bin/pkg/sql/sqlitelogictest/tests/local/local_test_/local_test.runfiles/com_github_cockroachdb_cockroach/external/com_github_cockroachdb_sqllogictest/test/index/view/1000/slt_good_0.test: 1012 statements
[09:18:09] --- progress: /home/roach/.cache/bazel/_bazel_roach/c5a4e7d36696d9cd970af2045211a7df/sandbox/processwrapper-sandbox/3669/execroot/com_github_cockroachdb_cockroach/bazel-out/k8-fastbuild/bin/pkg/sql/sqlitelogictest/tests/local/local_test_/local_test.runfiles/com_github_cockroachdb_cockroach/external/com_github_cockroachdb_sqllogictest/test/index/view/1000/slt_good_0.test: 1137 statements
[09:18:11] --- progress: /home/roach/.cache/bazel/_bazel_roach/c5a4e7d36696d9cd970af2045211a7df/sandbox/processwrapper-sandbox/3669/execroot/com_github_cockroachdb_cockroach/bazel-out/k8-fastbuild/bin/pkg/sql/sqlitelogictest/tests/local/local_test_/local_test.runfiles/com_github_cockroachdb_cockroach/external/com_github_cockroachdb_sqllogictest/test/index/view/1000/slt_good_0.test: 1339 statements
[09:18:13] --- progress: /home/roach/.cache/bazel/_bazel_roach/c5a4e7d36696d9cd970af2045211a7df/sandbox/processwrapper-sandbox/3669/execroot/com_github_cockroachdb_cockroach/bazel-out/k8-fastbuild/bin/pkg/sql/sqlitelogictest/tests/local/local_test_/local_test.runfiles/com_github_cockroachdb_cockroach/external/com_github_cockroachdb_sqllogictest/test/index/view/1000/slt_good_0.test: 1496 statements
[09:18:15] --- progress: /home/roach/.cache/bazel/_bazel_roach/c5a4e7d36696d9cd970af2045211a7df/sandbox/processwrapper-sandbox/3669/execroot/com_github_cockroachdb_cockroach/bazel-out/k8-fastbuild/bin/pkg/sql/sqlitelogictest/tests/local/local_test_/local_test.runfiles/com_github_cockroachdb_cockroach/external/com_github_cockroachdb_sqllogictest/test/index/view/1000/slt_good_0.test: 1543 statements
panic: test timed out after 1h59m55s

[michae2]

We think this is better now.

[yuzefovich]

My guess is that bumping the lower bound of workmem size is what did the trick.