Comment 6 for bug 1699529

This was reported for artful which is EOL nowadays.
But the very same RowSet error is still an issue and it seems that it blocks all i386-xenial tests since mid 2017 [1] - that is the last 41/41 tests.
I think we can agree that that seems pretty consistently broken for now.

All of the last errors were blocked on the very same JunitTest_dbaccess_complex test
$ check-autopkgtest-stats.sh -c 40 -p libreoffice -r xenial -a i386 -P 'gb_JunitTest_DEBUGRUN'
Check last 40 test results for src:libreoffice on releases 'xenial' on architectures 'i386'
Fetch Data to /tmp/tmp.zmMkCSCraz
Of the 40 last tests, we had these subtest failing per release/arch:

xenial
  i386
     40 junit-subsequentcheck (100.00%) FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF
Pattern found, sum/order found patterns
     40 make gb_JunitTest_DEBUGRUN=T JunitTest_dbaccess_comple

Other than stated before this is reproducible with i386 in VM:
$ sudo autopkgtest-buildvm-ubuntu-cloud -a i386 -r xenial -s 15G
# Note: I use autopkgtest from git
$ sudo ~/work/autopkgtest/autopkgtest/runner/autopkgtest --test-name=junit-subsequentcheck --no-built-binaries --apt-upgrade --shell-fail libreoffice_5.1.6~rc2-0ubuntu1~xenial6.dsc -- qemu --qemu-options='-cpu host' --ram-size=2048 --cpus 4 ~/work/autopkgtest-xenial-i386.img

When you log in you can isolate the failing test via:

$ cd /tmp/autopkgtest.*/build.*/src
$ make -rk OOO_TEST_SOFFICE=path:/usr/lib/libreoffice/program/soffice bridges_SELECTED_BRIDGE=foo JunitTest_dbaccess_complex

I'll attach some debug data I got that way for you to reconsider.

[1]: http://autopkgtest.ubuntu.com/packages/libr/libreoffice/xenial/i386