roachtest: schemachange/mixed-versions failed

[cockroach-teamcity]

roachtest.schemachange/mixed-versions failed with artifacts on master @ 3aa5bdf40527e2f60b179094403b4302a1c2cbe1:

(mixedversion.go:612).Run: mixed-version test failure while running step 7 (run "run schemachange workload and validation in mixed version"): full command output in run_063057.453204075_n4_COCKROACHRANDOMSEED6.log: COMMAND_PROBLEM: exit status 1
test artifacts and logs in: /artifacts/schemachange/mixed-versions/run_1

Parameters:

• ROACHTEST_arch=amd64
• ROACHTEST_cloud=gce
• ROACHTEST_coverageBuild=false
• ROACHTEST_cpu=4
• ROACHTEST_encrypted=false
• ROACHTEST_metamorphicBuild=false
• ROACHTEST_ssd=0

Help

See: roachtest README

See: How To Investigate (internal)

See: Grafana

Same failure on other branches

• roachtest: schemachange/mixed-versions failed #125617 roachtest: schemachange/mixed-versions failed [C-test-failure O-roachtest O-robot T-sql-foundations branch-release-24.1 release-blocker]
• roachtest: schemachange/mixed-versions failed [attempting to append refresh spans after the tracked timestamp has moved forward] #125379 roachtest: schemachange/mixed-versions failed [attempting to append refresh spans after the tracked timestamp has moved forward] [C-test-failure O-roachtest O-robot T-sql-queries branch-release-23.2]
• roachtest: schemachange/mixed-versions failed [debug doctor validation: existing descriptors that still need to be dropped] #124722 roachtest: schemachange/mixed-versions failed [debug doctor validation: existing descriptors that still need to be dropped] [C-test-failure O-roachtest O-robot P-2 T-sql-foundations branch-release-23.1.22-rc]

/cc @cockroachdb/sql-foundations

This test on roachdash | Improve this report!

Jira issue: CRDB-39588

[rafiss]

{
 "workerId": 4,
 "clientTimestamp": "06:31:05.936062",
 "ops": [
  "BEGIN",
  {
   "sql": "INSERT INTO schema_w1_9.table_w2_27 (\"%q\\vcol27_w2_28\",col27_w2_29,\"c%po\"\"%p😸l\"\"27_w2_30\") VALUES (111:::INT8,'=R C}]$6':::REFCURSOR,'C7D469B2/CA0B8075':::PG_LSN),((-67):::INT8,e'0{%\\x1f\\x1f)#\\x1fZ':::REFCURSOR,'B8C5EC29/3DB375C0':::PG_LSN)"
  }
 ],
 "expectedExecErrors": "",
 "expectedCommitErrors": "",
 "message": "***UNEXPECTED ERROR; Received an unexpected execution error.: ERROR: integer out of range (SQLSTATE 22003)",

This might be related to the bounds for the pg_lsn type.