Checkin 437849c80851da84 breaks FTS3 test on s390x
(1) By Reinhard Max (reimax) on 2024-12-10 15:36:12 [link] [source]
The above checkin is supposed to fix test fts3corrupt4-25.6, but actually breaks it on s390x:
! fts3corrupt4-25.6 expected: [1 {database disk image is malformed}]
! fts3corrupt4-25.6 got: [0 {}]
Non of SUSE's other architectures (x86_64, aarch64, ppc64le) shows this behavior.
For the failure to manifest it is enough to ./configure --enable-fts3 .
Other configure flags (especially the ones that enable fts4 and fts5) don't seem to matter.
For versions below that commit the error happens the other way around, if FTS3 is enabled, but FTS5 is not (as expected).
(2) By Richard Hipp (drh) on 2024-12-13 01:27:48 in reply to 1 [source]
Should be fixed by check-in 6216bfcb74273b78 on 2024-11-06. That fix did not make it into 3.47.2.
This is not an SQLite bug. It's a test case bug. The test case gives different answers on big-endian and little-endian systems. The older version of the test case you are running insisted on the little-endian answer.
The fix is queued for the 3.48.0 release. In the meantime, the error can be safely ignored.