Debian mips: Failed test 'Check expected t_009_tbl data on standby'

From: Christoph Berg <myon(at)debian(dot)org>
To: PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Debian mips: Failed test 'Check expected t_009_tbl data on standby'
Date: 2018-10-11 07:29:06
Message-ID: 20181011072906.GA32300@msg.df7cb.de
Views: Raw Message | Whole Thread | Download mbox
Thread:
Lists: pgsql-hackers

The 11rc1 build was failing on Debian mips:

cd /<<PKGBUILDDIR>>/build/../src/test/recovery && TESTDIR='/<<PKGBUILDDIR>>/build/src/test/recovery' PATH="/<<PKGBUILDDIR>>/build/tmp_install/usr/lib/postgresql/11/bin:$PATH" LD_LIBRARY_PATH="/<<PKGBUILDDIR>>/build/tmp_install/usr/lib/mips-linux-gnu" PGPORT='65432' PG_REGRESS='/<<PKGBUILDDIR>>/build/src/test/recovery/../../../src/test/regress/pg_regress' /usr/bin/prove -I /<<PKGBUILDDIR>>/build/../src/test/perl/ -I /<<PKGBUILDDIR>>/build/../src/test/recovery t/*.pl
t/001_stream_rep.pl .................. ok
t/002_archiving.pl ................... ok
t/003_recovery_targets.pl ............ ok
t/004_timeline_switch.pl ............. ok
t/005_replay_delay.pl ................ ok
t/006_logical_decoding.pl ............ ok
t/007_sync_rep.pl .................... ok
t/008_fsm_truncation.pl .............. ok

# Failed test 'Check expected t_009_tbl data on standby'
# at t/009_twophase.pl line 405.
# got: '1|issued to london
# 2|issued to london
# 5|issued to london
# 6|issued to london
# 9|issued to london
# 10|issued to london
# 11|issued to london
# 12|issued to london
# 13|issued to london
# 15|issued to london
# 16|issued to london
# 17|issued to london
# 18|issued to london
# 19|issued to london
# 20|issued to london
# 21|issued to london
# 22|issued to london
# 23|issued to paris
# 24|issued to paris
# 25|issued to london
# 26|issued to london
# |'
# expected: '1|issued to london
# 2|issued to london
# 5|issued to london
# 6|issued to london
# 9|issued to london
# 10|issued to london
# 11|issued to london
# 12|issued to london
# 13|issued to london
# 14|issued to london
# 15|issued to london
# 16|issued to london
# 17|issued to london
# 18|issued to london
# 19|issued to london
# 20|issued to london
# 21|issued to london
# 22|issued to london
# 23|issued to paris
# 24|issued to paris
# 25|issued to london
# 26|issued to london'
# Looks like you failed 1 test of 20.
t/009_twophase.pl ....................
Dubious, test returned 1 (wstat 256, 0x100)
Failed 1/20 subtests
t/010_logical_decoding_timelines.pl .. ok
t/011_crash_recovery.pl .............. ok
t/012_subtransactions.pl ............. ok
t/013_crash_restart.pl ............... ok
t/014_unlogged_reinit.pl ............. ok
t/015_promotion_pages.pl ............. ok

Test Summary Report
-------------------
t/009_twophase.pl (Wstat: 256 Tests: 20 Failed: 1)
Failed test: 19
Non-zero exit status: 1

The diff is that "14|issued to london" was expected, but "|" was
received.

https://buildd.debian.org/status/fetch.php?pkg=postgresql-11&arch=mips&ver=11~rc1-1&stamp=1539192131&raw=0

Unfortunately the build log does not contain the relevant
postmaster.log for this test.

The build succeeded when I retried it manually on a different box.

Is that something to be concerned about? JIT is active on this
platform, albeit with an older version (1:7~svn331965-1 vs 1:7-5).

Christoph

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Kyotaro HORIGUCHI 2018-10-11 08:04:53 Re: [HACKERS] WAL logging problem in 9.4.3?
Previous Message Dilip Kumar 2018-10-11 06:00:24 Undo worker and transaction rollback