Your message dated Wed, 12 Jan 2022 17:18:45 +0000
with message-id <e1n7hgn-0003oq...@fasolo.debian.org>
and subject line Bug#1001811: fixed in postgresql-mysql-fdw 2.7.0-2
has caused the Debian Bug report #1001811,
regarding postgresql-mysql-fdw: autopkgtest regression on armhf and i386: 
failed to look up symbol "evalexpr_19_0"
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1001811: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1001811
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: postgresql-mysql-fdw
Version: 2.7.0-1
X-Debbugs-CC: debian...@lists.debian.org
Severity: serious
User: debian...@lists.debian.org
Usertags: regression

Dear maintainer(s),

With a recent upload of postgresql-mysql-fdw the autopkgtest of postgresql-mysql-fdw fails in testing when that autopkgtest is run with the binary packages of postgresql-mysql-fdw from unstable. It passes when run with only packages from testing. In tabular form:

                       pass            fail
postgresql-mysql-fdw   from testing    2.7.0-1
all others             from testing    from testing

I copied some of the output at the bottom of this report.

Currently this regression is blocking the migration to testing [1]. Can you please investigate the situation and fix it?

More information about this bug and the reason for filing it can be found on
https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation

Paul

[1] https://qa.debian.org/excuses.php?package=postgresql-mysql-fdw

https://ci.debian.net/data/autopkgtest/testing/i386/p/postgresql-mysql-fdw/17609222/log.gz

== creating the MySQL test database
--------------
CREATE DATABASE mysql_fdw_regress
--------------

--------------
CREATE DATABASE mysql_fdw_regress1
--------------

--------------
CREATE USER 'edb'@'localhost' IDENTIFIED BY 'edb'
--------------

--------------
GRANT ALL PRIVILEGES ON mysql_fdw_regress.* TO 'edb'@'localhost'
--------------

--------------
GRANT ALL PRIVILEGES ON mysql_fdw_regress1.* TO 'edb'@'localhost'
--------------

### PostgreSQL 14 installcheck ###
Creating new PostgreSQL cluster 14/regress ...
/usr/lib/postgresql/14/lib/pgxs/src/makefiles/../../src/test/regress/pg_regress --inputdir=./ --bindir='/usr/lib/postgresql/14/bin' --dbname=contrib_regression server_options connection_validation dml select pushdown join_pushdown aggregate_pushdown
(using postmaster on localhost, port 5433)
============== dropping database "contrib_regression" ==============
NOTICE:  database "contrib_regression" does not exist, skipping
DROP DATABASE
============== creating database "contrib_regression" ==============
CREATE DATABASE
ALTER DATABASE
============== running regression test queries        ==============
test server_options               ... ok          107 ms
test connection_validation        ... ok           70 ms
test dml                          ... ok          132 ms
test select                       ... ok          555 ms
test pushdown                     ... ok          123 ms
test join_pushdown                ... ok         1620 ms
test aggregate_pushdown           ... FAILED     2824 ms

======================
 1 of 7 tests failed. ======================

The differences that caused some tests to fail can be viewed in the
file "/tmp/autopkgtest-lxc.r_7rxru0/downtmp/build.z8H/src/regression.diffs". A copy of the test summary that you see above is saved in the file "/tmp/autopkgtest-lxc.r_7rxru0/downtmp/build.z8H/src/regression.out".

make: *** [/usr/lib/postgresql/14/lib/pgxs/src/makefiles/pgxs.mk:433: installcheck] Error 1 *** /tmp/pg_virtualenv.joAylJ/log/postgresql-14-regress.log (last 100 lines) *** 2021-12-16 10:13:48.401 UTC [4153] LOG: starting PostgreSQL 14.1 (Debian 14.1-1) on i686-pc-linux-gnu, compiled by gcc (Debian 11.2.0-10) 11.2.0, 32-bit 2021-12-16 10:13:48.402 UTC [4153] LOG: listening on IPv6 address "::1", port 5433 2021-12-16 10:13:48.402 UTC [4153] LOG: listening on IPv4 address "127.0.0.1", port 5433 2021-12-16 10:13:48.402 UTC [4153] LOG: listening on Unix socket "/var/run/postgresql/.s.PGSQL.5433" 2021-12-16 10:13:48.403 UTC [4154] LOG: database system was shut down at 2021-12-16 10:13:48 UTC 2021-12-16 10:13:48.407 UTC [4153] LOG: database system is ready to accept connections 2021-12-16 10:13:50.785 UTC [4205] postgres@contrib_regression WARNING: MySQL secure authentication is off 2021-12-16 10:13:50.791 UTC [4205] postgres@contrib_regression ERROR: "fetch_size" requires an integer value between 1 to 4294967295 2021-12-16 10:13:50.791 UTC [4205] postgres@contrib_regression STATEMENT: ALTER FOREIGN TABLE table30000 OPTIONS ( SET fetch_size '-60000'); 2021-12-16 10:13:50.792 UTC [4205] postgres@contrib_regression ERROR: "fetch_size" requires an integer value between 1 to 4294967295 2021-12-16 10:13:50.792 UTC [4205] postgres@contrib_regression STATEMENT: ALTER FOREIGN TABLE table30000 OPTIONS ( SET fetch_size '123abc'); 2021-12-16 10:13:50.792 UTC [4205] postgres@contrib_regression ERROR: "fetch_size" requires an integer value between 1 to 4294967295 2021-12-16 10:13:50.792 UTC [4205] postgres@contrib_regression STATEMENT: ALTER FOREIGN TABLE table30000 OPTIONS ( SET fetch_size '999999999999999999999'); 2021-12-16 10:13:50.794 UTC [4205] postgres@contrib_regression ERROR: reconnect requires a Boolean value 2021-12-16 10:13:50.794 UTC [4205] postgres@contrib_regression STATEMENT: ALTER SERVER reconnect1 OPTIONS ( SET reconnect 'abc1' ); 2021-12-16 10:13:50.950 UTC [4228] postgres@contrib_regression ERROR: first column of remote table must be unique for INSERT/UPDATE/DELETE operation 2021-12-16 10:13:50.950 UTC [4228] postgres@contrib_regression STATEMENT: INSERT INTO fdw126_ft3 VALUES(1, 'One'); 2021-12-16 10:13:50.952 UTC [4228] postgres@contrib_regression ERROR: first column of remote table must be unique for INSERT/UPDATE/DELETE operation 2021-12-16 10:13:50.952 UTC [4228] postgres@contrib_regression STATEMENT: UPDATE fdw126_ft3 SET b = 'one' WHERE a = 1; 2021-12-16 10:13:50.953 UTC [4228] postgres@contrib_regression ERROR: first column of remote table must be unique for INSERT/UPDATE/DELETE operation 2021-12-16 10:13:50.953 UTC [4228] postgres@contrib_regression STATEMENT: DELETE FROM fdw126_ft3 WHERE a = 1; 2021-12-16 10:13:50.954 UTC [4228] postgres@contrib_regression ERROR: relation mysql_fdw_regress1.nosuchtable does not exist 2021-12-16 10:13:50.954 UTC [4228] postgres@contrib_regression STATEMENT: ANALYZE fdw126_ft4; 2021-12-16 10:13:50.954 UTC [4228] postgres@contrib_regression ERROR: relation mysql_fdw_regress2.numbers does not exist 2021-12-16 10:13:50.954 UTC [4228] postgres@contrib_regression STATEMENT: ANALYZE fdw126_ft5; 2021-12-16 10:13:50.965 UTC [4228] postgres@contrib_regression WARNING: skipping "f_empdata" --- cannot vacuum non-tables or special system tables 2021-12-16 10:13:50.965 UTC [4228] postgres@contrib_regression WARNING: skipping "f_empdata" --- cannot vacuum non-tables or special system tables 2021-12-16 10:13:50.966 UTC [4228] postgres@contrib_regression WARNING: skipping "f_empdata" --- cannot vacuum non-tables or special system tables 2021-12-16 10:13:50.966 UTC [4228] postgres@contrib_regression WARNING: skipping "f_empdata" --- cannot analyze this foreign table 2021-12-16 10:13:50.967 UTC [4228] postgres@contrib_regression WARNING: skipping "f_empdata" --- cannot analyze this foreign table 2021-12-16 10:13:50.967 UTC [4228] postgres@contrib_regression WARNING: skipping "f_empdata" --- cannot vacuum non-tables or special system tables 2021-12-16 10:13:50.975 UTC [4228] postgres@contrib_regression ERROR: row identifier column update is not supported 2021-12-16 10:13:50.975 UTC [4228] postgres@contrib_regression STATEMENT: UPDATE fdw126_ft1 SET stu_dept = 201, stu_id = 10 WHERE stu_id = 1; 2021-12-16 10:13:50.977 UTC [4228] postgres@contrib_regression ERROR: row identifier column update is not supported 2021-12-16 10:13:50.977 UTC [4228] postgres@contrib_regression STATEMENT: UPDATE fdw126_ft1 SET stu_dept = 301 WHERE stu_id = 1; 2021-12-16 10:13:50.986 UTC [4228] postgres@contrib_regression ERROR: row identifier column update is not supported 2021-12-16 10:13:50.986 UTC [4228] postgres@contrib_regression STATEMENT: UPDATE fdw193_ft1 SET stu_dept = 301 WHERE stu_id = 'aa'; 2021-12-16 10:13:50.988 UTC [4228] postgres@contrib_regression ERROR: row identifier column update is not supported 2021-12-16 10:13:50.988 UTC [4228] postgres@contrib_regression STATEMENT: UPDATE fdw193_ft1 SET stu_dept = 401 WHERE stu_id = 'aa'; 2021-12-16 10:13:50.988 UTC [4228] postgres@contrib_regression ERROR: cannot copy from foreign table "f_mysql_test" 2021-12-16 10:13:50.988 UTC [4228] postgres@contrib_regression HINT: Try the COPY (SELECT ...) TO variant. 2021-12-16 10:13:50.988 UTC [4228] postgres@contrib_regression STATEMENT: COPY f_mysql_test TO stdout; 2021-12-16 10:13:50.989 UTC [4228] postgres@contrib_regression ERROR: cannot copy from foreign table "f_mysql_test" 2021-12-16 10:13:50.989 UTC [4228] postgres@contrib_regression HINT: Try the COPY (SELECT ...) TO variant. 2021-12-16 10:13:50.989 UTC [4228] postgres@contrib_regression STATEMENT: COPY f_mysql_test (a) TO stdout; 2021-12-16 10:13:51.388 UTC [4237] postgres@contrib_regression ERROR: invalid reference to FROM-clause entry for table "t1" at character 88 2021-12-16 10:13:51.388 UTC [4237] postgres@contrib_regression DETAIL: The combining JOIN type must be INNER or LEFT for a LATERAL reference. 2021-12-16 10:13:51.388 UTC [4237] postgres@contrib_regression STATEMENT: SELECT t1.c1, t3.c1, t3.t1_c8 FROM f_test_tbl1 t1 RIGHT JOIN LATERAL (
          SELECT t2.c1, t1.c8 AS t1_c8 FROM f_test_tbl2 t2) t3 ON t3.c1 = 
t3.t1_c8
          ORDER BY 1, 2, 3;
2021-12-16 10:13:51.421 UTC [4237] postgres@contrib_regression ERROR: invalid input value for enum size_t: "big" at character 34 2021-12-16 10:13:51.421 UTC [4237] postgres@contrib_regression STATEMENT: INSERT INTO f_enum_t1 VALUES (4, 'big'); 2021-12-16 10:13:51.476 UTC [4237] postgres@contrib_regression ERROR: system attribute "xmin" can't be fetched from remote relation 2021-12-16 10:13:51.476 UTC [4237] postgres@contrib_regression STATEMENT: SELECT xmin FROM f_test_tbl1; 2021-12-16 10:13:51.476 UTC [4237] postgres@contrib_regression ERROR: system attribute "ctid" can't be fetched from remote relation 2021-12-16 10:13:51.476 UTC [4237] postgres@contrib_regression STATEMENT: SELECT ctid, xmax, tableoid FROM f_test_tbl1; 2021-12-16 10:13:51.477 UTC [4237] postgres@contrib_regression ERROR: system attribute "xmax" can't be fetched from remote relation 2021-12-16 10:13:51.477 UTC [4237] postgres@contrib_regression STATEMENT: SELECT xmax, c1 FROM f_test_tbl1; 2021-12-16 10:13:51.477 UTC [4237] postgres@contrib_regression ERROR: system attribute "tableoid" can't be fetched from remote relation 2021-12-16 10:13:51.477 UTC [4237] postgres@contrib_regression STATEMENT: SELECT count(tableoid) FROM f_test_tbl1; 2021-12-16 10:13:51.504 UTC [4237] postgres@contrib_regression WARNING: skipping import for relation "test_set" 2021-12-16 10:13:51.504 UTC [4237] postgres@contrib_regression DETAIL: MySQL SET columns are not supported. 2021-12-16 10:13:54.618 UTC [4265] postgres@contrib_regression WARNING: failed to resolve name __mulodi4 2021-12-16 10:13:54.619 UTC [4265] postgres@contrib_regression ERROR: failed to look up symbol "evalexpr_19_0" 2021-12-16 10:13:54.619 UTC [4265] postgres@contrib_regression STATEMENT: SELECT sum(c2) * (random() <= 1)::int AS sum FROM fdw132_t1 ORDER BY 1;
Dropping cluster 14/regress ...
**** regression.diffs ****
diff -U3 /tmp/autopkgtest-lxc.r_7rxru0/downtmp/build.z8H/src/expected/aggregate_pushdown.out /tmp/autopkgtest-lxc.r_7rxru0/downtmp/build.z8H/src/results/aggregate_pushdown.out --- /tmp/autopkgtest-lxc.r_7rxru0/downtmp/build.z8H/src/expected/aggregate_pushdown.out 2021-11-18 08:59:41.000000000 +0000 +++ /tmp/autopkgtest-lxc.r_7rxru0/downtmp/build.z8H/src/results/aggregate_pushdown.out 2021-12-16 10:13:56.127310576 +0000
@@ -629,11 +629,8 @@
 (7 rows)
  SELECT sum(c2) * (random() <= 1)::int AS sum FROM fdw132_t1 ORDER BY 1;
- sum ------
- 300
-(1 row)
-
+WARNING:  failed to resolve name __mulodi4
+ERROR:  failed to look up symbol "evalexpr_19_0"
 -- LATERAL join, with parameterization
 EXPLAIN (VERBOSE, COSTS OFF)
SELECT c2, sum FROM fdw132_t1 t1, lateral (SELECT sum(t2.c1 + t1.c1) sum FROM fdw132_t2 t2 GROUP BY t2.c1) qry WHERE t1.c2 * 2 = qry.sum and t1.c2 > 10 ORDER BY 1;
### End 14 installcheck (FAILED with exit code 1) ###
== dropping the MySQL test database
--------------
DROP USER 'edb'@'localhost'
--------------

--------------
DROP DATABASE mysql_fdw_regress
--------------

--------------
DROP DATABASE mysql_fdw_regress1
--------------

autopkgtest [10:13:57]: test installcheck

Attachment: OpenPGP_signature
Description: OpenPGP digital signature


--- End Message ---
--- Begin Message ---
Source: postgresql-mysql-fdw
Source-Version: 2.7.0-2
Done: Christoph Berg <m...@debian.org>

We believe that the bug you reported is fixed in the latest version of
postgresql-mysql-fdw, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1001...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Christoph Berg <m...@debian.org> (supplier of updated postgresql-mysql-fdw 
package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Format: 1.8
Date: Wed, 12 Jan 2022 17:28:21 +0100
Source: postgresql-mysql-fdw
Built-For-Profiles: nocheck
Architecture: source
Version: 2.7.0-2
Distribution: unstable
Urgency: medium
Maintainer: Debian PostgreSQL Maintainers <team+postgre...@tracker.debian.org>
Changed-By: Christoph Berg <m...@debian.org>
Closes: 1001811
Changes:
 postgresql-mysql-fdw (2.7.0-2) unstable; urgency=medium
 .
   * Disable jit for tests; works around "failed to resolve name __mulodi4".
     Cf. https://github.com/EnterpriseDB/mysql_fdw/pull/227.
     (Closes: 1001811)
Checksums-Sha1:
 105882e88d726e5a8d13bb2e6bb85797ff8341ab 2271 postgresql-mysql-fdw_2.7.0-2.dsc
 e3cf6a4b34d066c81998b55c564a61cea86df56f 6276 
postgresql-mysql-fdw_2.7.0-2.debian.tar.xz
Checksums-Sha256:
 ab5511b8095dd0e0b798bf0a7370d742a2b6db0bcc1034c34d9ed314c79dcb46 2271 
postgresql-mysql-fdw_2.7.0-2.dsc
 a8e62dc3a3045512358d899ccbf0ca5c21e308843d8aac220c8aef2c9e56dc51 6276 
postgresql-mysql-fdw_2.7.0-2.debian.tar.xz
Files:
 9a24e6047ab29e75dee68a8846d718b5 2271 database optional 
postgresql-mysql-fdw_2.7.0-2.dsc
 0d47305334ade3f5e8dd763c0f1cdeeb 6276 database optional 
postgresql-mysql-fdw_2.7.0-2.debian.tar.xz

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCAAdFiEEXEj+YVf0kXlZcIfGTFprqxLSp64FAmHfChIACgkQTFprqxLS
p65Exw//bZ5VihyIXz8ZbW9Ac3sBn2Axsw/FEZWfQWqWPbyR5mW4+4uIF393j+7u
dje7lXLYwzcY4RG+esvSbC5HLhGlZy2kPZlKmCyJjsRdyfms/3ik7SQPKUi5Y6P5
MbkV80TC7aAEJlu1xdtL3mI/JT7hLPLO+t72JCgX9PeAJH8Jx8srJbXgQ/EoYd5v
t+5lxrrmytQUiNvqd1HbAoNgOvMXt0ATCO8fJaCht5rC5ZXLsaTUp8a1kXPOt2Hq
1A9/u3oCth1GwNxd4wCGQWIiCopj+9KDUdNLjB2n+idBKg3d5h96SEkC9l6wtMxJ
uMiK2ZLy13Md3ZUc/eHnvlCfEa6MVUrpeWeh7WKpMfxRQUCnxcLDhfA8YbaoOyHo
DQOhDdkPgvWrtZXAqccVqGbKyuTxb0r76sOuzUwC8X/dzKZGYRzlDNZxTxYDAxJh
hRTWPNEzcprbA1qlwagauuEDLoC0+vBsi7ouJg2ZYxXQSds/pEMmoq+to14+Rsr5
YiH3WTWH4wJwbAjG64lFuabLZvbKJIzuhgehLzpg0DXxM0oFyPOss87j1+1lYagV
psiCWkge17W3e6JYnj2ZiUBuy4XFSKJm1N0n/0cHrLDDxTGGv/ld3hVBsHfJ4oIU
FquFLpJlRxlZ1VsKzIew4eO70+sD2Ot9l1eXxb6xkro6RlucYkE=
=YVAD
-----END PGP SIGNATURE-----

--- End Message ---

Reply via email to