Your message dated Sun, 27 Feb 2022 12:20:18 +0000
with message-id <e1noixc-0002ou...@fasolo.debian.org>
and subject line Bug#998553: fixed in libdbi-drivers 0.9.0-10
has caused the Debian Bug report #998553,
regarding libdbi-drivers: FTBFS: 211104  9:49:12 [ERROR] mysqld got signal 11 ;
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.)


-- 
998553: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998553
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libdbi-drivers
Version: 0.9.0-9
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20211104 ftbfs-bookworm

Hi,

During a rebuild of all packages in sid, your package failed to build
on amd64.


Relevant part (hopefully):
> make[1]: Entering directory '/<<PKGBUILDDIR>>/debian/buildtests'
> gcc test_dbi_lib.c -export-dynamic -shared -Wl,-soname,libtest_dbi_lib.so -o 
> libtest_dbi_lib.so -ldbi -fPIC
> test_dbi_lib.c: In function ‘init_db’:
> test_dbi_lib.c:26:5: warning: ‘dbi_initialize’ is deprecated 
> [-Wdeprecated-declarations]
>    26 |     return dbi_initialize(dir);
>       |     ^~~~~~
> In file included from test_dbi_lib.c:20:
> /usr/include/dbi/dbi.h:169:27: note: declared here
>   169 | int LIBDBI_API_DEPRECATED dbi_initialize(const char *driverdir);
>       |                           ^~~~~~~~~~~~~~
> gcc test_dl.c -o test_dl -ldl
> rm -rf all-libs
> mkdir -p all-libs 
> olddir=`pwd` && cd ../.. && rootdir=`pwd` && for f in `find drivers -name 
> 'libdbd*.so'` ; do  ln -vs $rootdir/$f $olddir/all-libs ; done
> '/<<PKGBUILDDIR>>/debian/buildtests/all-libs/libdbdpgsql.so' -> 
> '/<<PKGBUILDDIR>>/drivers/pgsql/.libs/libdbdpgsql.so'
> '/<<PKGBUILDDIR>>/debian/buildtests/all-libs/libdbdfreetds.so' -> 
> '/<<PKGBUILDDIR>>/drivers/freetds/.libs/libdbdfreetds.so'
> '/<<PKGBUILDDIR>>/debian/buildtests/all-libs/libdbdsqlite3.so' -> 
> '/<<PKGBUILDDIR>>/drivers/sqlite3/.libs/libdbdsqlite3.so'
> '/<<PKGBUILDDIR>>/debian/buildtests/all-libs/libdbdmysql.so' -> 
> '/<<PKGBUILDDIR>>/drivers/mysql/.libs/libdbdmysql.so'
> ./test_dl G all-libs
> num drivers = 4
> ./test_dl N all-libs
> num drivers = 4
> make[1]: Leaving directory '/<<PKGBUILDDIR>>/debian/buildtests'
> # Testing sqlite3
> mkdir -p /<<PKGBUILDDIR>>/debian/sqlite3tests
> ( echo i; \
>       echo n; \
>       echo ./drivers/sqlite3/.libs; \
>       echo sqlite3; \
>       echo /<<PKGBUILDDIR>>/debian/sqlite3tests; \
>       echo libdbitest; ) | ./tests/test_dbi
> 
> libdbi-drivers test program: $Id: test_dbi.c,v 1.72 2013/02/24 15:06:57 
> mhoenicka Exp $
> 
> test instance-based (i) or legacy (l) libdbi interface? [i] log query (y|n)? 
> [n] libdbi driver directory? [/usr/lib/x86_64-linux-gnu/dbd] 1 drivers 
> available: sqlite3 
> test which driver? database directory? [DEFAULT] database name? [libdbitest] 
> encoding? [] 
> Connection information:
> --------------------
>       Legacy mode:           0
>       Log query:             0
>       Driverdir:             ./drivers/sqlite3/.libs
>       Drivername:            sqlite3
>       Dbdir:                 /<<PKGBUILDDIR>>/debian/sqlite3tests
>       Initial Database:      libdbitest
>       Database:              libdbitest
>       Username:              
>       Password:              
>       Hostname:              
>       Version:               
>       Initial tables schema: CREATE TABLE test_datatypes ( the_char 
> CHAR,the_uchar CHAR,the_short SMALLINT,the_ushort SMALLINT,the_long 
> INT,the_ulong INT,the_longlong BIGINT,the_ulonglong BIGINT,the_float 
> FLOAT4,the_double FLOAT8,the_driver_string 
> VARCHAR(255),the_conn_quoted_string VARCHAR(255),the_conn_quoted_string_copy 
> VARCHAR(255),the_conn_escaped_string 
> VARCHAR(255),the_conn_escaped_string_copy VARCHAR(255),the_numstring 
> VARCHAR(255),the_empty_string VARCHAR(255),the_null_string 
> VARCHAR(255),the_binary_quoted_string BLOB,the_binary_escaped_string 
> BLOB,the_datetime DATETIME,the_datetime_tz DATETIME,the_date DATE,the_time 
> TIME,the_time_tz TIME,id INTEGER AUTO INCREMENT)
>       Initial sub schema:
>         0: 
>         1: 
>         2: 
>         3: 
>         4: 
>       Initial data schema:   INSERT INTO test_datatypes 
> (the_char,the_uchar,the_short,the_ushort,the_long,the_ulong,the_longlong,the_ulonglong,the_float,the_double,the_conn_quoted_string,the_conn_quoted_string_copy,the_conn_escaped_string,the_conn_escaped_string_copy,the_numstring,the_empty_string,the_null_string,the_binary_quoted_string,the_binary_escaped_string,the_datetime,the_datetime_tz,the_date,the_time,the_time_tz)
>  VALUES 
> (-127,127,-32768,32767,-2147483648,2147483647,-9223372036854775807,9223372036854775807,3.402823466E+38,1.7976931348623157E+307,'Can
>  ''we'' "quote" this properly?','Can ''we'' "quote" this properly?','Can 
> ''we'' "escape" this properly?','Can ''we'' "escape" this 
> properly?','-54321','',NULL,'@A?B&C','@A?B&C','2001-12-31 
> 23:59:59','2001-12-31 23:59:59 
> -10:00','2001-12-31','23:59:59','23:59:59-10:00')
> 
> Begin tests:
> --------------------
> Running "libdbi framework test"...
> Running "libdbi framework test"...
> Running "libdbi framework test"...
> Running "libdbi framework test"...
> Running "libdbi framework test"...
> Running "libdbi framework test"...
> Running "libdbi framework test"...
> Running "libdbi framework test"...
> Running "libdbi framework test"...
> Running "libdbi framework test"...
> Running "libdbi framework test"...
> Running "libdbi framework test"...
> Running "libdbi framework test"...
> Running "libdbi framework test"...
> Running "libdbi framework test"...
> Running "libdbi framework test"...
> Running "libdbi framework test"...
> Running "libdbi framework test"...
> Running "libdbi framework test"...
> Running "libdbi framework test"...
> Running "libdbi framework test"...
> Running "libdbi framework test"...
> Running "libdbi framework test"...
> Running "libdbi framework test"...
> Running "libdbi framework test"...
> Running "libdbi framework test"...
> Running "libdbi framework test"...
> Running "libdbi framework test"...
> Running "libdbi framework test"...
> Running "libdbi framework test"...
> Running "libdbi framework test"...
> Running "libdbi framework test"...
> Running "libdbi framework test"...
> Running "libdbi framework test"...
> Running "libdbi framework test"...
> Running "libdbi framework test"...
> Running "libdbi framework test"...
> Running "libdbi framework test"...
> Running "libdbi framework test"...
> Running "libdbi framework test"...
> Running "libdbi framework test"...
> Running "libdbi framework test"...
> Running "libdbi framework test"...
> Running "libdbi framework test"...
> Running "libdbi framework test"...
> Running "libdbi framework test"...
> Running "libdbi framework test"...
> Running "libdbi framework test"...
> Running "libdbi framework test"...
> Running "libdbi framework test"...
> Running "libdbi framework test"...
> Running "libdbi framework test"...
> Running "libdbi framework test"...
> Running "libdbi framework test"...
> Running "libdbi framework test"...
> Running "libdbi framework test"...
> Running "libdbi framework test"...
> Running "libdbi framework test"...
> Running "libdbi framework test"...
> Running "libdbi framework test"...
> Running "libdbi framework test"...
> Running "libdbi framework test"...
> Running "libdbi framework test"...
> Running "libdbi framework test"...
> Running "libdbi framework test"...
> Running "libdbi framework test"...
> Running "libdbi framework test"...
> Running "libdbi framework test"...
> Running "libdbi framework test"...
> Running "libdbi framework test"...
> Running "libdbi framework test"...
> Running "libdbi framework test"...
> Running "libdbi framework test"...
> Running "libdbi framework test"...
> Running "libdbi framework test"...
> Running "libdbi framework test"...
> Running "libdbi framework test"...
> Running "libdbi framework test"...
> Running "libdbi framework test"...
> Running "libdbi framework test"...
> Running "libdbi framework test"...
> Running "libdbi framework test"...
> Running "libdbi framework test"...
> Running "libdbi framework test"...
> Running "libdbi framework test"...
> Running "libdbi framework test"...
> Running "libdbi framework test"...
> Running "libdbi framework test"...
> Running "libdbi framework test"...
> Running "libdbi framework test"...
> Running "libdbi framework test"...
> Running "libdbi framework test"...
> Running "libdbi framework test"...
> Running "libdbi framework test"...
> Running "libdbi framework test"...
> Running "libdbi framework test"...
> Running "libdbi framework test"...
> Running "libdbi framework test"...
> Running "libdbi framework test"...
> Completed "libdbi framework test": 395 passes, 0 failures, 0 exceptions.
> rm -rf /<<PKGBUILDDIR>>/debian/sqlite3tests
> # Testing MySQL and Postgress
> chmod +x ./debian/test_mysql.sh
> ./debian/test_mysql.sh
> chown: cannot access '/usr/lib/mysql/plugin/auth_pam_tool_dir/auth_pam_tool': 
> Permission denied
> Couldn't set an owner to 
> '/usr/lib/mysql/plugin/auth_pam_tool_dir/auth_pam_tool'.
> It must be root, the PAM authentication plugin doesn't work otherwise..
> 
> chown: changing ownership of '/usr/lib/mysql/plugin/auth_pam_tool_dir': 
> Operation not permitted
> Cannot change ownership of the '/usr/lib/mysql/plugin/auth_pam_tool_dir' 
> directory
> to the 'user42' user. Check that you have the necessary permissions and try 
> again.
> 
> Installing MariaDB/MySQL system tables in '/tmp/tmp.QTH9UWFKRs' ...
> OK
> 
> To start mysqld at boot time you have to copy
> support-files/mysql.server to the right place for your system
> 
> 
> Two all-privilege accounts were created.
> One is root@localhost, it has no password, but you need to
> be system 'root' user to connect. Use, for example, sudo mysql
> The second is user42@localhost, it has no password either, but
> you need to be the system 'user42' user to connect.
> After connecting you can set the password, if you would need to be
> able to connect as any of these users with a password and without sudo
> 
> See the MariaDB Knowledgebase at https://mariadb.com/kb or the
> MySQL manual for more instructions.
> 
> You can start the MariaDB daemon with:
> cd '/usr' ; /usr/bin/mysqld_safe --datadir='/tmp/tmp.QTH9UWFKRs'
> 
> You can test the MariaDB daemon with mysql-test-run.pl
> cd '/usr/mysql-test' ; perl mysql-test-run.pl
> 
> Please report any problems at https://mariadb.org/jira
> 
> The latest information about MariaDB is available at https://mariadb.org/.
> You can find additional information about the MySQL part at:
> https://dev.mysql.com
> Consider joining MariaDB's strong and vibrant community:
> https://mariadb.org/get-involved/
> 
> pinging mysqld./usr/bin/mysqladmin: connect to server at 'localhost' failed
> error: 'Can't connect to local MySQL server through socket 
> '/tmp/tmp.QTH9UWFKRs/mysql.sock' (2)'
> Check that mysqld is running and that the socket: 
> '/tmp/tmp.QTH9UWFKRs/mysql.sock' exists!
> 2021-11-04  9:49:07 0 [Note] Using unique option prefix 'skip-grant' is 
> error-prone and can break in the future. Please use the full name 
> 'skip-grant-tables' instead.
> 2021-11-04  9:49:07 0 [Note] /usr/sbin/mysqld (mysqld 10.5.12-MariaDB-1) 
> starting as process 18041 ...
> 2021-11-04  9:49:08 0 [Note] InnoDB: Uses event mutexes
> 2021-11-04  9:49:08 0 [Note] InnoDB: Compressed tables use zlib 1.2.11
> 2021-11-04  9:49:08 0 [Note] InnoDB: Number of pools: 1
> 2021-11-04  9:49:08 0 [Note] InnoDB: Using crc32 + pclmulqdq instructions
> 2021-11-04  9:49:08 0 [Note] mysqld: O_TMPFILE is not supported on /tmp 
> (disabling future attempts)
> 2021-11-04  9:49:08 0 [Note] InnoDB: Using Linux native AIO
> 2021-11-04  9:49:08 0 [Note] InnoDB: Initializing buffer pool, total size = 
> 134217728, chunk size = 134217728
> 2021-11-04  9:49:08 0 [Note] InnoDB: Completed initialization of buffer pool
> 2021-11-04  9:49:08 0 [Note] InnoDB: 128 rollback segments are active.
> 2021-11-04  9:49:08 0 [Note] InnoDB: Creating shared tablespace for temporary 
> tables
> 2021-11-04  9:49:08 0 [Note] InnoDB: Setting file './ibtmp1' size to 12 MB. 
> Physically writing the file full; Please wait ...
> 2021-11-04  9:49:08 0 [Note] InnoDB: File './ibtmp1' size is now 12 MB.
> 2021-11-04  9:49:08 0 [Note] InnoDB: 10.5.12 started; log sequence number 
> 45094; transaction id 20
> 2021-11-04  9:49:08 0 [Note] Plugin 'FEEDBACK' is disabled.
> 2021-11-04  9:49:08 0 [Note] InnoDB: Loading buffer pool(s) from 
> /tmp/tmp.QTH9UWFKRs/ib_buffer_pool
> 2021-11-04  9:49:08 0 [Note] InnoDB: Buffer pool(s) load completed at 211104  
> 9:49:08
> 2021-11-04  9:49:08 0 [Note] Reading of all Master_info entries succeeded
> 2021-11-04  9:49:08 0 [Note] Added new Master_info '' to hash table
> 2021-11-04  9:49:08 0 [Note] /usr/sbin/mysqld: ready for connections.
> Version: '10.5.12-MariaDB-1'  socket: '/tmp/tmp.QTH9UWFKRs/mysql.sock'  port: 
> 0  Debian 11
> mysqld is alive
> 
> libdbi-drivers test program: $Id: test_dbi.c,v 1.72 2013/02/24 15:06:57 
> mhoenicka Exp $
> 
> test instance-based (i) or legacy (l) libdbi interface? [i] log query (y|n)? 
> [n] libdbi driver directory? [/usr/lib/x86_64-linux-gnu/dbd] 1 drivers 
> available: mysql 
> test which driver? 
> database administrator name? 
> database administrator password? 
> database hostname? [(blank for local socket if possible)] database name? 
> [libdbitest] encoding? [] 
> Connection information:
> --------------------
>       Legacy mode:           0
>       Log query:             0
>       Driverdir:             ./drivers/mysql/.libs
>       Drivername:            mysql
>       Dbdir:                 
>       Initial Database:      mysql
>       Database:              libdbitest
>       Username:              root
>       Password:              
>       Hostname:              localhost
>       Version:               
>       Initial tables schema: CREATE TABLE test_datatypes ( the_char 
> TINYINT,the_uchar TINYINT,the_short SMALLINT,the_ushort SMALLINT,the_long 
> INT,the_ulong INT,the_longlong BIGINT,the_ulonglong BIGINT,the_float 
> FLOAT4,the_double FLOAT8,the_conn_quoted_string 
> VARCHAR(255),the_conn_quoted_string_copy VARCHAR(255),the_conn_escaped_string 
> VARCHAR(255),the_conn_escaped_string_copy VARCHAR(255),the_numstring 
> VARCHAR(255),the_empty_string VARCHAR(255),the_null_string 
> VARCHAR(255),the_binary_quoted_string BLOB,the_binary_escaped_string 
> BLOB,the_datetime DATETIME,the_datetime_tz DATETIME,the_date DATE,the_time 
> TIME,the_time_tz TIME,id INT AUTO_INCREMENT,PRIMARY KEY (id)) ENGINE=InnoDB
>       Initial sub schema:
>         0: 
>         1: 
>         2: 
>         3: 
>         4: 
>       Initial data schema:   INSERT INTO test_datatypes 
> (the_char,the_uchar,the_short,the_ushort,the_long,the_ulong,the_longlong,the_ulonglong,the_float,the_double,the_conn_quoted_string,the_conn_quoted_string_copy,the_conn_escaped_string,the_conn_escaped_string_copy,the_numstring,the_empty_string,the_null_string,the_binary_quoted_string,the_binary_escaped_string,the_datetime,the_datetime_tz,the_date,the_time,the_time_tz)
>  VALUES 
> (-127,127,-32768,32767,-2147483648,2147483647,-9223372036854775807,9223372036854775807,3.402823466E+38,1.7976931348623157E+307,'Can
>  ''we'' "quote" this properly?','Can ''we'' "quote" this properly?','Can 
> ''we'' "escape" this properly?','Can ''we'' "escape" this 
> properly?','-54321','',NULL,'AB\0C\'D','AB\0C\'D','2001-12-31 
> 23:59:59','2001-12-31 23:59:59','2001-12-31','23:59:59','23:59:59')
> 
> Begin tests:
> --------------------
> Running "libdbi framework test"...
> Running "libdbi framework test"...
> Running "libdbi framework test"...
> Running "libdbi framework test"...
> Running "libdbi framework test"...
> Running "libdbi framework test"...
> Running "libdbi framework test"...
> Running "libdbi framework test"...
> Running "libdbi framework test"...
> Running "libdbi framework test"...
> Running "libdbi framework test"...
> Running "libdbi framework test"...
> Running "libdbi framework test"...
> Running "libdbi framework test"...
> Running "libdbi framework test"...
> Running "libdbi framework test"...
> Running "libdbi framework test"...
> Running "libdbi framework test"...
> Running "libdbi framework test"...
> Running "libdbi framework test"...
> Running "libdbi framework test"...
> Running "libdbi framework test"...
> Running "libdbi framework test"...
> Running "libdbi framework test"...
> Running "libdbi framework test"...
> Running "libdbi framework test"...
> Running "libdbi framework test"...
> Running "libdbi framework test"...
> Running "libdbi framework test"...
> Running "libdbi framework test"...
> Running "libdbi framework test"...
> Running "libdbi framework test"...
> Running "libdbi framework test"...
> Running "libdbi framework test"...
> Running "libdbi framework test"...
> Running "libdbi framework test"...
> Running "libdbi framework test"...
> Running "libdbi framework test"...
> Running "libdbi framework test"...
> Running "libdbi framework test"...
> Running "libdbi framework test"...
> Running "libdbi framework test"...
> Running "libdbi framework test"...
> Running "libdbi framework test"...
> Running "libdbi framework test"...
> Running "libdbi framework test"...
> Running "libdbi framework test"...
> Running "libdbi framework test"...
> Running "libdbi framework test"...
> Running "libdbi framework test"...
> Running "libdbi framework test"...
> Running "libdbi framework test"...
> Running "libdbi framework test"...
> Running "libdbi framework test"...
> Running "libdbi framework test"...
> Running "libdbi framework test"...
> Running "libdbi framework test"...
> Running "libdbi framework test"...
> Running "libdbi framework test"...
> Running "libdbi framework test"...
> Running "libdbi framework test"...
> Running "libdbi framework test"...
> Running "libdbi framework test"...
> Running "libdbi framework test"...
> Running "libdbi framework test"...
> Running "libdbi framework test"...
> Running "libdbi framework test"...
> Running "libdbi framework test"...
> Running "libdbi framework test"...
> Running "libdbi framework test"...
> Running "libdbi framework test"...
> Running "libdbi framework test"...
> Running "libdbi framework test"...
> Running "libdbi framework test"...
> Running "libdbi framework test"...
> Running "libdbi framework test"...
> Running "libdbi framework test"...
> Running "libdbi framework test"...
> Running "libdbi framework test"...
> Running "libdbi framework test"...
> Running "libdbi framework test"...
> Running "libdbi framework test"...
> Running "libdbi framework test"...
> Running "libdbi framework test"...
> Running "libdbi framework test"...
> Running "libdbi framework test"...
> Running "libdbi framework test"...
> Running "libdbi framework test"...
> Running "libdbi framework test"...
> Running "libdbi framework test"...
> Running "libdbi framework test"...
> Running "libdbi framework test"...
> Running "libdbi framework test"...
> Running "libdbi framework test"...
> Running "libdbi framework test"...
> Running "libdbi framework test"...
> Running "libdbi framework test"...
> Running "libdbi framework test"...
> Running "libdbi framework test"...
> Running "libdbi framework test"...
> Completed "libdbi framework test": 409 passes, 0 failures, 0 exceptions.
> 2021-11-04  9:49:12 0 [Note] /usr/sbin/mysqld (initiated by: [user42] @ 
> localhost []): Normal shutdown
> 211104  9:49:12 [ERROR] mysqld got signal 11 ;
> This could be because you hit a bug. It is also possible that this binary
> or one of the libraries it was linked against is corrupt, improperly built,
> or misconfigured. This error can also be caused by malfunctioning hardware.
> 
> To report this bug, see https://mariadb.com/kb/en/reporting-bugs
> 
> 2021-11-04  9:49:12 0 [Note] InnoDB: FTS optimize thread exiting.
> We will try our best to scrape up some info that will hopefully help
> diagnose the problem, but since we have already crashed, 
> something is definitely wrong and this may fail.
> 
> Server version: 10.5.12-MariaDB-1
> key_buffer_size=134217728
> read_buffer_size=131072
> max_used_connections=2
> max_threads=153
> thread_count=0
> It is possible that mysqld could use up to 
> key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 467871 
> K  bytes of memory
> Hope that's ok; if not, decrease some variables in the equation.
> 
> Thread pointer: 0x0
> Attempting backtrace. You can use the following information to find out
> where mysqld died. If you see no messages after this, something went
> terribly wrong...
> stack_bottom = 0x0 thread_stack 0x49000
> 2021-11-04  9:49:12 0 [Note] InnoDB: Starting shutdown...
> 2021-11-04  9:49:12 0 [Note] InnoDB: Dumping buffer pool(s) to 
> /tmp/tmp.QTH9UWFKRs/ib_buffer_pool
> 2021-11-04  9:49:12 0 [Note] InnoDB: Buffer pool(s) dump completed at 211104  
> 9:49:12
> ??:0(my_print_stacktrace)[0x564a18fc6a0e]
> ??:0(handle_fatal_signal)[0x564a18ad1a45]
> ??:0(__restore_rt)[0x7f5dad5a08e0]
> ??:0(OPENSSL_LH_insert)[0x7f5dad741295]
> ??:0(ERR_load_ERR_strings)[0x7f5dad71ee53]
> ??:0(ERR_clear_last_mark)[0x7f5dad720209]
> ??:0(HMAC_CTX_get_md)[0x7f5dad73e9f9]
> ??:0(__pthread_once_slow)[0x7f5dad59da7f]
> ??:0(CRYPTO_THREAD_run_once)[0x7f5dad7a9e79]
> ??:0(OPENSSL_init_crypto)[0x7f5dad73ef2b]
> ??:0(ERR_get_state)[0x7f5dad71f5d6]
> ??:0(ERR_clear_error)[0x7f5dad71f709]
> ??:0(handle_one_connection)[0x564a189d455e]
> ??:0(MyCTX_nopad::finish(unsigned char*, unsigned int*))[0x564a18d0d432]
> ??:0(start_thread)[0x7f5dad595eae]
> ??:0(clone)[0x7f5dad16ca5f]
> The manual page at 
> https://mariadb.com/kb/en/how-to-produce-a-full-stack-trace-for-mysqld/ 
> contains
> information that should help you find out what is causing the crash.
> Writing a core file...
> Working directory at /tmp/tmp.QTH9UWFKRs
> Resource Limits:
> Limit                     Soft Limit           Hard Limit           Units     
> Max cpu time              unlimited            unlimited            seconds   
> Max file size             unlimited            unlimited            bytes     
> Max data size             unlimited            unlimited            bytes     
> Max stack size            8388608              unlimited            bytes     
> Max core file size        0                    unlimited            bytes     
> Max resident set          unlimited            unlimited            bytes     
> Max processes             62929                62929                processes 
> Max open files            32186                32186                files     
> Max locked memory         67108864             67108864             bytes     
> Max address space         unlimited            unlimited            bytes     
> Max file locks            unlimited            unlimited            locks     
> Max pending signals       62929                62929                signals   
> Max msgqueue size         819200               819200               bytes     
> Max nice priority         0                    0                    
> Max realtime priority     0                    0                    
> Max realtime timeout      unlimited            unlimited            us        
> Core pattern: core
> 
> Warning;  Aborted waiting on pid file: 
> '/tmp/tmp.QTH9UWFKRs/ip-172-31-9-125.pid' after 3600 seconds
> make: *** [debian/rules:80: test-stamp] Error 255


The full build log is available from:
http://qa-logs.debian.net/2021/11/04/libdbi-drivers_0.9.0-9_unstable.log

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

If you reassign this bug to another package, please marking it as 'affects'-ing
this package. See https://www.debian.org/Bugs/server-control#affects

If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.

--- End Message ---
--- Begin Message ---
Source: libdbi-drivers
Source-Version: 0.9.0-10
Done: Laszlo Boszormenyi (GCS) <g...@debian.org>

We believe that the bug you reported is fixed in the latest version of
libdbi-drivers, 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 998...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Laszlo Boszormenyi (GCS) <g...@debian.org> (supplier of updated libdbi-drivers 
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: SHA512

Format: 1.8
Date: Sun, 27 Feb 2022 11:02:33 +0100
Source: libdbi-drivers
Architecture: source
Version: 0.9.0-10
Distribution: unstable
Urgency: medium
Maintainer: Laszlo Boszormenyi (GCS) <g...@debian.org>
Changed-By: Laszlo Boszormenyi (GCS) <g...@debian.org>
Closes: 961282 998553
Changes:
 libdbi-drivers (0.9.0-10) unstable; urgency=medium
 .
   * Don't use time zone literals with MariaDB (closes: #998553).
   * Sync with Ubuntu.
 .
   [ Sergio Durigan Junior <sergio.duri...@canonical.com> ]
   * d/p/mysql-8.0: fixes for build against MySQL 8.0 (closes: #961282).
   * d/test_mysql.sh: fixes for MySQL 8.0.
   * d/p/test_mysql_date_tz.patch: fix MySQL test timezone inputs.
Checksums-Sha1:
 2233d08bd32cce60af031eab1c478efbb1912e01 2259 libdbi-drivers_0.9.0-10.dsc
 03ea84f7216e9cf13bbe03797e458951079bb0ec 14508 
libdbi-drivers_0.9.0-10.debian.tar.xz
Checksums-Sha256:
 3b609acd4c8087ed7c9bff2c2637d55c9d352710e1e82a4c7f507912e481ab2d 2259 
libdbi-drivers_0.9.0-10.dsc
 cc2f28a937bc78c4a3f19c523fde21dae80962bf80dba90eaa9bf9f96adf42b1 14508 
libdbi-drivers_0.9.0-10.debian.tar.xz
Files:
 dcb873e240054fbd81bd51f51304892a 2259 libs optional libdbi-drivers_0.9.0-10.dsc
 7dd63b5b97849d7fceeaef1a9a795463 14508 libs optional 
libdbi-drivers_0.9.0-10.debian.tar.xz

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

iQIzBAEBCgAdFiEEfYh9yLp7u6e4NeO63OMQ54ZMyL8FAmIbZgMACgkQ3OMQ54ZM
yL8F1RAArvDK6bpyL6sr9yig5X5sv6sX9e++kw7q1uVMClpveRM02B5MPg+NA7wh
ZVHU6ZHB+7Qaq+A65Op2zS4bbF0yn+gla22chI2gscppPQzSTiIBEQ88ZSzZw1id
U7MdPY0RCooVHblP2njd97frvk8K+YPrsr6qjmyRQg+/lzZCKnP0h0ZuI9fhUzr4
nxMYNA6HeJPXOwS1P2jsfuvcF392+gud759Fk/U1PrMTYYwQ52ARbs7D6OdO2/bl
6/MZS7Adnvfx5kw8LIjbRelNS1nibyea4LvXqlPXAjm+Ji9aH5GHdz/gpZHNp3l9
3BrxQxFZuAtoxmkPpJ1QO/2CBxCjJMnf3GFeqZQTQnOvvlQfRTkkdkfzvvQ1JFIP
ombSmTzQEYBHm7V4Gk7DlziaHOgKWkV/Vq32OJkyg4AhOXKHLiYhyyQHyzU4rHQ7
iEj4dwb3biWxnQ5rZU47wiEz+PdAuSP8o4XCX0t6OAgtqCnKHAdUhxydhgAhTudZ
//bAQItglRyt+Bb5D6vKe5A+KUbVcY7lifdHafiASjpuZWEXuMovU+1Co7fdEPJ9
yoqWbIjWYpsZ5bzJeoWOhPa1wtrCvxt7QRBUFxHzgiQrCFaEc6e99wArreB/r8ef
3Ddk6OW+N4wVNWfQXtYn77pEm/rjarYEa9O7s9TOBAedxQ7OBr0=
=q3qs
-----END PGP SIGNATURE-----

--- End Message ---

Reply via email to