So ignoring these as acceptable issues:
- T: pgsql armhf failures due to lxc/lxd (ok)
- X: pgsql armhf/s390x failures due to lxc/lxd (ok)
- X: mimeo armhf failures due to lxc/lxd (ok)
Also the i386 libreoffice regression I've seen on xenial is known to be flaky since [1] and unrelated to the upload. But that can be re-tried until it is green if needed.
With that in mind all tests are good.
I also did a minor check install/upgrade and reuse of DB which was good.
The Mini Test that I did on top of the self tests the build and dep8 already exercises:
# Env prep
git clone https://github.com/akopytov/sysbench.git
apt install build-essential
apt-get build-dep sysbench
cd sysbench/
./autogen.sh
./configure --with-pgsql
make
make install
#psql setup
postgres=# CREATE USER sbtest WITH PASSWORD 'sbtest';
CREATE ROLE
postgres=# CREATE DATABASE sbtest;
CREATE DATABASE
postgres=# GRANT ALL PRIVILEGES ON DATABASE sbtest to sbtest;
# Then run
/usr/local/bin/sysbench oltp_read_only --db-driver=pgsql --pgsql-password="sbtest" prepare
/usr/local/bin/sysbench oltp_read_only --db-driver=pgsql --pgsql-password="sbtest" run
# Now upgrade postgresql - the DB should still be intact for a re-run
/usr/local/bin/sysbench oltp_read_only --db-driver=pgsql --pgsql-password="sbtest" run
# If this does not work either the DB took damage on upgrade or the server didn't restart properly
That said setting verification-done (for only known issues being left) as on past MREs
All good, some dep8's are known to be failing, quoting Pitti from [1]
"These are fallout from moving from LXC to LXD. For devel I fixed the latter in https:/ /anonscm. debian. org/cgit/ pkg-postgresql/ postgresql- common. git/commit/ ?id=fc40fc34ce -- functionally everything is correct, the test just failed on unexpected stderr output from a warning in netstat."
So ignoring these as acceptable issues:
- T: pgsql armhf failures due to lxc/lxd (ok)
- X: pgsql armhf/s390x failures due to lxc/lxd (ok)
- X: mimeo armhf failures due to lxc/lxd (ok)
Also the i386 libreoffice regression I've seen on xenial is known to be flaky since [1] and unrelated to the upload. But that can be re-tried until it is green if needed.
With that in mind all tests are good. /github. com/akopytov/ sysbench. git
I also did a minor check install/upgrade and reuse of DB which was good.
The Mini Test that I did on top of the self tests the build and dep8 already exercises:
# Env prep
git clone https:/
apt install build-essential
apt-get build-dep sysbench
cd sysbench/
./autogen.sh
./configure --with-pgsql
make
make install
#psql setup
postgres=# CREATE USER sbtest WITH PASSWORD 'sbtest';
CREATE ROLE
postgres=# CREATE DATABASE sbtest;
CREATE DATABASE
postgres=# GRANT ALL PRIVILEGES ON DATABASE sbtest to sbtest;
# Then run bin/sysbench oltp_read_only --db-driver=pgsql --pgsql- password= "sbtest" prepare bin/sysbench oltp_read_only --db-driver=pgsql --pgsql- password= "sbtest" run
/usr/local/
/usr/local/
# Now upgrade postgresql - the DB should still be intact for a re-run bin/sysbench oltp_read_only --db-driver=pgsql --pgsql- password= "sbtest" run
/usr/local/
# If this does not work either the DB took damage on upgrade or the server didn't restart properly
That said setting verification-done (for only known issues being left) as on past MREs
[1]: https:/ /bugs.launchpad .net/ubuntu/ +source/ postgresql- 9.5/+bug/ 1637236/ comments/ 8