roachtest: pg_regress failed

cockroach-teamcity commented 1 month ago

roachtest.pg_regress failed with artifacts on master @ 5cc8013ada42f9ea03eda661a4f178c141f4f24d:

++ 1785378053 | pg_proc_oid_idx
++ 3833625957 | pg_timezone_names_name_idx
++ 1384570493 | pg_type_oid_idx
++(30 rows)

  -- Cross-check against pg_type entry
  -- NOTE: we allow attstorage to be 'plain' even when typstorage is not;
-@@ -613,10 +944,7 @@
+@@ -613,10 +949,7 @@
        EXISTS(select 1 from pg_catalog.pg_type where
               oid = r.rngsubtype and typelem != 0 and
               typsubscript = 'array_subscript_handler'::regproc)));
@@ -42782,7 +42783,7 @@
  -- canonical function, if any, had better match the range type
  SELECT r.rngtypid, r.rngsubtype, p.proname
  FROM pg_range r JOIN pg_proc p ON p.oid = r.rngcanonical
-@@ -639,10 +967,7 @@
+@@ -639,10 +972,7 @@
  SELECT r.rngtypid, r.rngsubtype, r.rngmultitypid
  FROM pg_range r
  WHERE r.rngmultitypid IS NULL OR r.rngmultitypid = 0;
@@ -42794,7 +42795,7 @@
  -- Create a table that holds all the known in-core data types and leave it
  -- around so as pg_upgrade is able to test their binary compatibility.
  CREATE TABLE tab_core_types AS SELECT
-@@ -709,6 +1034,13 @@
+@@ -709,6 +1039,13 @@
    '{(2020-01-02 03:04:05, 2021-02-03 06:07:08)}'::tsmultirange,
    '(2020-01-02 03:04:05, 2021-02-03 06:07:08)'::tstzrange,
    '{(2020-01-02 03:04:05, 2021-02-03 06:07:08)}'::tstzmultirange;
@@ -42808,7 +42809,7 @@
  -- Sanity check on the previous table, checking that all core types are
  -- included in this table.
  SELECT oid, typname, typtype, typelem, typarray
-@@ -736,7 +1068,4 @@
+@@ -736,7 +1073,4 @@
                      WHERE a.atttypid=t.oid AND
                            a.attnum > 0 AND
                            a.attrelid='tab_core_types'::regclass);
@@ -135525,7 +135526,7 @@
  DROP OWNED BY regress_priv_user1;
  DROP USER regress_priv_user1;
  DROP USER regress_priv_user2;
-+ERROR:  cannot drop role/user regress_priv_user2: grants still exist on root.public.priv_testtype1, root.public._priv_testtype1
++ERROR:  cannot drop role/user regress_priv_user2: grants still exist on root.public._priv_testtype1, root.public.priv_testtype1
  DROP USER regress_priv_user3;
  DROP USER regress_priv_user4;
 +ERROR:  cannot drop role/user regress_priv_user4: grants still exist on root.public.mtarget
If the diff is expected, copy regression.diffs from the test artifacts to pkg/cmd/roachtest/testdata/regression.diffs
test artifacts and logs in: /artifacts/pg_regress/cpu_arch=arm64/run_1

Parameters:

ROACHTEST_arch=arm64
ROACHTEST_cloud=gce
ROACHTEST_coverageBuild=false
ROACHTEST_cpu=4
ROACHTEST_encrypted=false
ROACHTEST_runtimeAssertionsBuild=false
ROACHTEST_ssd=0
Help

See: roachtest README

See: How To Investigate (internal)

See: Grafana

_{This test on roachdash | Improve this report!

Jira issue: CRDB-42193}

cockroach-teamcity commented 1 month ago

roachtest.pg_regress failed with artifacts on master @ 5cc8013ada42f9ea03eda661a4f178c141f4f24d:

-+ 3649927600 | pg_proc_oid_idx
-+  883735674 | pg_timezone_names_name_idx
-+ 3008021490 | pg_type_oid_idx
-+(28 rows)
++ 3176850730 | pg_attrdef_adrelid_idx
++ 2917114457 | pg_attribute_attrelid_idx
++ 2397641923 | pg_class_oid_idx
++ 3742718928 | pg_constraint_conrelid_idx
++ 4169400142 | pg_namespace_oid_idx
++ 1785378053 | pg_proc_oid_idx
++ 3833625957 | pg_timezone_names_name_idx
++ 1384570493 | pg_type_oid_idx
++(30 rows)

  -- Cross-check against pg_type entry
  -- NOTE: we allow attstorage to be 'plain' even when typstorage is not;
-@@ -613,10 +944,7 @@
+@@ -613,10 +949,7 @@
        EXISTS(select 1 from pg_catalog.pg_type where
               oid = r.rngsubtype and typelem != 0 and
               typsubscript = 'array_subscript_handler'::regproc)));
@@ -42782,7 +42787,7 @@
  -- canonical function, if any, had better match the range type
  SELECT r.rngtypid, r.rngsubtype, p.proname
  FROM pg_range r JOIN pg_proc p ON p.oid = r.rngcanonical
-@@ -639,10 +967,7 @@
+@@ -639,10 +972,7 @@
  SELECT r.rngtypid, r.rngsubtype, r.rngmultitypid
  FROM pg_range r
  WHERE r.rngmultitypid IS NULL OR r.rngmultitypid = 0;
@@ -42794,7 +42799,7 @@
  -- Create a table that holds all the known in-core data types and leave it
  -- around so as pg_upgrade is able to test their binary compatibility.
  CREATE TABLE tab_core_types AS SELECT
-@@ -709,6 +1034,13 @@
+@@ -709,6 +1039,13 @@
    '{(2020-01-02 03:04:05, 2021-02-03 06:07:08)}'::tsmultirange,
    '(2020-01-02 03:04:05, 2021-02-03 06:07:08)'::tstzrange,
    '{(2020-01-02 03:04:05, 2021-02-03 06:07:08)}'::tstzmultirange;
@@ -42808,7 +42813,7 @@
  -- Sanity check on the previous table, checking that all core types are
  -- included in this table.
  SELECT oid, typname, typtype, typelem, typarray
-@@ -736,7 +1068,4 @@
+@@ -736,7 +1073,4 @@
                      WHERE a.atttypid=t.oid AND
                            a.attnum > 0 AND
                            a.attrelid='tab_core_types'::regclass);
If the diff is expected, copy regression.diffs from the test artifacts to pkg/cmd/roachtest/testdata/regression.diffs
test artifacts and logs in: /artifacts/pg_regress/run_1

Parameters:

ROACHTEST_arch=amd64
ROACHTEST_cloud=gce
ROACHTEST_coverageBuild=false
ROACHTEST_cpu=4
ROACHTEST_encrypted=false
ROACHTEST_runtimeAssertionsBuild=false
ROACHTEST_ssd=0
Help

See: roachtest README

See: How To Investigate (internal)

See: Grafana

_{This test on roachdash | Improve this report!}

cockroach-teamcity commented 1 month ago

roachtest.pg_regress failed with artifacts on master @ 5cc8013ada42f9ea03eda661a4f178c141f4f24d:

++ 1785378053 | pg_proc_oid_idx
++ 3833625957 | pg_timezone_names_name_idx
++ 1384570493 | pg_type_oid_idx
++(30 rows)

  -- Cross-check against pg_type entry
  -- NOTE: we allow attstorage to be 'plain' even when typstorage is not;
-@@ -613,10 +944,7 @@
+@@ -613,10 +949,7 @@
        EXISTS(select 1 from pg_catalog.pg_type where
               oid = r.rngsubtype and typelem != 0 and
               typsubscript = 'array_subscript_handler'::regproc)));
@@ -42782,7 +42787,7 @@
  -- canonical function, if any, had better match the range type
  SELECT r.rngtypid, r.rngsubtype, p.proname
  FROM pg_range r JOIN pg_proc p ON p.oid = r.rngcanonical
-@@ -639,10 +967,7 @@
+@@ -639,10 +972,7 @@
  SELECT r.rngtypid, r.rngsubtype, r.rngmultitypid
  FROM pg_range r
  WHERE r.rngmultitypid IS NULL OR r.rngmultitypid = 0;
@@ -42794,7 +42799,7 @@
  -- Create a table that holds all the known in-core data types and leave it
  -- around so as pg_upgrade is able to test their binary compatibility.
  CREATE TABLE tab_core_types AS SELECT
-@@ -709,6 +1034,13 @@
+@@ -709,6 +1039,13 @@
    '{(2020-01-02 03:04:05, 2021-02-03 06:07:08)}'::tsmultirange,
    '(2020-01-02 03:04:05, 2021-02-03 06:07:08)'::tstzrange,
    '{(2020-01-02 03:04:05, 2021-02-03 06:07:08)}'::tstzmultirange;
@@ -42808,7 +42813,7 @@
  -- Sanity check on the previous table, checking that all core types are
  -- included in this table.
  SELECT oid, typname, typtype, typelem, typarray
-@@ -736,7 +1068,4 @@
+@@ -736,7 +1073,4 @@
                      WHERE a.atttypid=t.oid AND
                            a.attnum > 0 AND
                            a.attrelid='tab_core_types'::regclass);
@@ -135525,7 +135530,7 @@
  DROP OWNED BY regress_priv_user1;
  DROP USER regress_priv_user1;
  DROP USER regress_priv_user2;
-+ERROR:  cannot drop role/user regress_priv_user2: grants still exist on root.public.priv_testtype1, root.public._priv_testtype1
++ERROR:  cannot drop role/user regress_priv_user2: grants still exist on root.public._priv_testtype1, root.public.priv_testtype1
  DROP USER regress_priv_user3;
  DROP USER regress_priv_user4;
 +ERROR:  cannot drop role/user regress_priv_user4: grants still exist on root.public.mtarget
If the diff is expected, copy regression.diffs from the test artifacts to pkg/cmd/roachtest/testdata/regression.diffs
test artifacts and logs in: /artifacts/pg_regress/run_1

Parameters:

ROACHTEST_arch=amd64
ROACHTEST_cloud=gce
ROACHTEST_coverageBuild=false
ROACHTEST_cpu=4
ROACHTEST_encrypted=false
ROACHTEST_runtimeAssertionsBuild=false
ROACHTEST_ssd=0
Help

See: roachtest README

See: How To Investigate (internal)

See: Grafana

_{This test on roachdash | Improve this report!}

cockroach-teamcity commented 1 month ago

roachtest.pg_regress failed with artifacts on master @ 83589fb87caa92fb42e83994f1691978f37e4cbb:

++ 1785378053 | pg_proc_oid_idx
++ 3833625957 | pg_timezone_names_name_idx
++ 1384570493 | pg_type_oid_idx
++(30 rows)

  -- Cross-check against pg_type entry
  -- NOTE: we allow attstorage to be 'plain' even when typstorage is not;
-@@ -613,10 +944,7 @@
+@@ -613,10 +949,7 @@
        EXISTS(select 1 from pg_catalog.pg_type where
               oid = r.rngsubtype and typelem != 0 and
               typsubscript = 'array_subscript_handler'::regproc)));
@@ -42782,7 +42787,7 @@
  -- canonical function, if any, had better match the range type
  SELECT r.rngtypid, r.rngsubtype, p.proname
  FROM pg_range r JOIN pg_proc p ON p.oid = r.rngcanonical
-@@ -639,10 +967,7 @@
+@@ -639,10 +972,7 @@
  SELECT r.rngtypid, r.rngsubtype, r.rngmultitypid
  FROM pg_range r
  WHERE r.rngmultitypid IS NULL OR r.rngmultitypid = 0;
@@ -42794,7 +42799,7 @@
  -- Create a table that holds all the known in-core data types and leave it
  -- around so as pg_upgrade is able to test their binary compatibility.
  CREATE TABLE tab_core_types AS SELECT
-@@ -709,6 +1034,13 @@
+@@ -709,6 +1039,13 @@
    '{(2020-01-02 03:04:05, 2021-02-03 06:07:08)}'::tsmultirange,
    '(2020-01-02 03:04:05, 2021-02-03 06:07:08)'::tstzrange,
    '{(2020-01-02 03:04:05, 2021-02-03 06:07:08)}'::tstzmultirange;
@@ -42808,7 +42813,7 @@
  -- Sanity check on the previous table, checking that all core types are
  -- included in this table.
  SELECT oid, typname, typtype, typelem, typarray
-@@ -736,7 +1068,4 @@
+@@ -736,7 +1073,4 @@
                      WHERE a.atttypid=t.oid AND
                            a.attnum > 0 AND
                            a.attrelid='tab_core_types'::regclass);
@@ -135525,7 +135530,7 @@
  DROP OWNED BY regress_priv_user1;
  DROP USER regress_priv_user1;
  DROP USER regress_priv_user2;
-+ERROR:  cannot drop role/user regress_priv_user2: grants still exist on root.public.priv_testtype1, root.public._priv_testtype1
++ERROR:  cannot drop role/user regress_priv_user2: grants still exist on root.public._priv_testtype1, root.public.priv_testtype1
  DROP USER regress_priv_user3;
  DROP USER regress_priv_user4;
 +ERROR:  cannot drop role/user regress_priv_user4: grants still exist on root.public.mtarget
If the diff is expected, copy regression.diffs from the test artifacts to pkg/cmd/roachtest/testdata/regression.diffs
test artifacts and logs in: /artifacts/pg_regress/run_1

Parameters:

ROACHTEST_arch=amd64
ROACHTEST_cloud=gce
ROACHTEST_coverageBuild=false
ROACHTEST_cpu=4
ROACHTEST_encrypted=false
ROACHTEST_runtimeAssertionsBuild=false
ROACHTEST_ssd=0
Help

See: roachtest README

See: How To Investigate (internal)

See: Grafana

_{This test on roachdash | Improve this report!}

cockroach-teamcity commented 1 month ago

roachtest.pg_regress failed with artifacts on master @ 5400cb9a70e63bfe1aa2849a566c195ad63130d1:

++NOTICE:  using sequential values in a primary key does not perform as well as using random UUIDs. See https://www.cockroachlabs.com/docs/v24.3/serial.html
  insert into rewriteme
       select x * 1.001 from generate_series(1, 500) as t(x);
  alter table rewriteme alter column foo type numeric;
 -ERROR:  rewrites not allowed
 -CONTEXT:  PL/pgSQL function test_evtrig_no_rewrite() line 3 at RAISE
 +ERROR:  ALTER COLUMN TYPE from float to decimal is only supported experimentally
-+HINT:  See: https://go.crdb.dev/issue-v/49329/dev
++HINT:  See: https://go.crdb.dev/issue-v/49329/v24.3
 +--
 +you can enable alter column type general support by running ``SET enable_experimental_alter_column_type_general = true``
  alter table rewriteme add column baz int default 0;
@@ -264658,7 +264597,7 @@
   alter column foo type numeric(10,4);
 -NOTICE:  Table 'rewriteme' is being rewritten (reason = 4)
 +ERROR:  ALTER COLUMN TYPE from float to decimal is only supported experimentally
-+HINT:  See: https://go.crdb.dev/issue-v/49329/dev
++HINT:  See: https://go.crdb.dev/issue-v/49329/v24.3
 +--
 +you can enable alter column type general support by running ``SET enable_experimental_alter_column_type_general = true``
  -- matview rewrite when changing access method
@@ -264680,7 +264619,7 @@
  -- shouldn't trigger a table_rewrite event
  alter table rewriteme alter column foo type numeric(12,4);
 +ERROR:  ALTER COLUMN TYPE from float to decimal is only supported experimentally
-+HINT:  See: https://go.crdb.dev/issue-v/49329/dev
++HINT:  See: https://go.crdb.dev/issue-v/49329/v24.3
 +--
 +you can enable alter column type general support by running ``SET enable_experimental_alter_column_type_general = true``
  begin;
@@ -264720,7 +264659,7 @@
 +alter type rewritetype alter attribute a type text cascade
 +                                                          ^
 +HINT:  You have attempted to use a feature that is not yet implemented.
-+See: https://go.crdb.dev/issue-v/48701/dev
++See: https://go.crdb.dev/issue-v/48701/v24.3
  -- but this doesn't work
  create table rewritemetoo3 (a rewritetype);
  alter type rewritetype alter attribute a type varchar cascade;
@@ -264730,7 +264669,7 @@
 +alter type rewritetype alter attribute a type varchar cascade
 +                                                             ^
 +HINT:  You have attempted to use a feature that is not yet implemented.
-+See: https://go.crdb.dev/issue-v/48701/dev
++See: https://go.crdb.dev/issue-v/48701/v24.3
  drop table rewriteme;
  drop event trigger no_rewrite_allowed;
 +ERROR:  at or near "event": syntax error
If the diff is expected, copy regression.diffs from the test artifacts to pkg/cmd/roachtest/testdata/regression.diffs
test artifacts and logs in: /artifacts/pg_regress/run_1

Parameters:

ROACHTEST_arch=amd64
ROACHTEST_cloud=gce
ROACHTEST_coverageBuild=false
ROACHTEST_cpu=4
ROACHTEST_encrypted=false
ROACHTEST_runtimeAssertionsBuild=false
ROACHTEST_ssd=0
Help

See: roachtest README

See: How To Investigate (internal)

See: Grafana

_{This test on roachdash | Improve this report!}

cockroachdb / cockroach

roachtest: pg_regress failed #130735